MariaDB log - and why in docker - there are always such errors in MariaDB

Seafile Server
,
#1

2023-11-12 13:19:56 0 [Note] mariadbd: ready for connections.

Version: '11.1.2-MariaDB-1:11.1.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution

2023-11-12 13:19:58 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'root' host: '172.18.0.5' (Got an error reading communication packets)

2023-11-12 13:19:59 5 [Warning] Aborted connection 5 to db: 'ccnet_db' user: 'seafile' host: '172.18.0.5' (Got an error reading communication packets)

2023-11-12 13:20:00 6 [Warning] Aborted connection 6 to db: 'seafile_db' user: 'seafile' host: '172.18.0.5' (Got an error reading communication packets)

2023-11-12 13:20:03 7 [Warning] Aborted connection 7 to db: 'seahub_db' user: 'seafile' host: '172.18.0.5' (Got an error reading communication packets)

2023-11-12 13:20:03 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'root' host: '172.18.0.5' (Got an error reading communication packets)

2023-11-12 13:20:09 10 [Warning] Aborted connection 10 to db: 'seahub_db' user: 'seafile' host: '172.18.0.5' (Got an error reading communication packets)

    2023-11-12 14:09:00 0 [Note] mariadbd: ready for connections.
    Version: '11.1.2-MariaDB-1:11.1.2+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
    2023-11-12 14:09:00 0 [Note] InnoDB: Buffer pool(s) load completed at 231112 14:09:00
    2023-11-12 14:09:02 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'seafile' host: '172.18.0.5' (Got an error reading communication packets)

it does not affect the work
just can someone explain why this is so ? and why not do it without these errors ?

#2

There are a few things that you can do to reduce the number of “Aborted connection” errors in your MariaDB logs:

  • Make sure that the client applications that are connecting to the database server are up to date and using the latest version of the MariaDB client library.
  • Check the network connection between the client applications and the database server to make sure that it is stable and reliable.
  • Monitor the client applications that are connecting to the database server for any errors or crashes.
  • If you are using a load balancer to distribute traffic between multiple database servers, make sure that the load balancer is properly configured.:v: