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 ?
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.
pm1234
April 19, 2025, 5:19pm
3
seafile 12, new docker based installation, has a similar issue:
from docker compose logs:
…
seafile-mysql | 2025-04-19 8:31:54 23733 [Warning] Aborted connection 23733 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 23734 [Warning] Aborted connection 23734 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 23735 [Warning] Aborted connection 23735 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 24108 [Warning] Aborted connection 24108 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 24109 [Warning] Aborted connection 24109 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 24110 [Warning] Aborted connection 24110 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 24111 [Warning] Aborted connection 24111 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 24485 [Warning] Aborted connection 24485 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 8:31:54 24488 [Warning] Aborted connection 24488 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 10:31:54 25241 [Warning] Aborted connection 25241 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 24490 [Warning] Aborted connection 24490 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 24491 [Warning] Aborted connection 24491 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 24864 [Warning] Aborted connection 24864 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 24866 [Warning] Aborted connection 24866 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 24865 [Warning] Aborted connection 24865 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 24867 [Warning] Aborted connection 24867 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 25242 [Warning] Aborted connection 25242 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-04-19 11:31:54 25244 [Warning] Aborted connection 25244 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
etc …