Mysql db Error reading communication packets

Seafile Server
,
1

Fresh install of seafile, from the default docker-compose.yml

Gives the timeout error below.

Same error as forum topic 18808, two years ago, which has no resolution.

Is it a –wait-timeout= issue? Can’t be network performance on docker local.

How to debug this issue?

Is v12 worth a try instead?

Greetings to contributors and collaborators.

REPOSITORY TAG IMAGE ID CREATED SIZE
seafileltd/seafile-mc 11.0-latest 50af26877cb9 10 months ago 1.38GB

seafile            | Successfully created seafile admin
seafile            | ----------------------------------------
seafile            | 
seafile            | 
seafile            | 
seafile-mysql      | 2025-09-08 20:02:13 11 [Warning] Aborted connection 11 to db: 'seahub_db' user: 'seafile' host: '172.21.0.4' (Got an error reading communication packets)
seafile-mysql      | 2025-09-08 20:02:13 13 [Warning] Aborted connection 13 to db: 'seafile_db' user: 'seafile' host: '172.21.0.4' (Got an error reading communication packets)
1 Like
2

This error usually means the clients of MySQL (seahub/seaf-server and other components in Seafile server) forget to close the connection to MySQL after open and use the connection.

We have fixed a few of such places in the latest version. You can give the latest version a try.

These errors do not affect the function of the server. If there are not much of such errors, they can be ignored.

3

still ocurring with lastest 13 version

grep image seafile-server.yml

image: ${SEAFILE_DB_IMAGE:-mariadb:10.11}
image: ${SEAFILE_MEMCACHED_IMAGE:-memcached:1.6.29}
image: ${SEAFILE_IMAGE:-seafileltd/seafile-mc:13.0-latest}

docker images | grep seafile-mc

seafileltd/seafile-mc 13.0-latest 8f4c83d8cd41 6 weeks ago 1.57GB

docker pull seafileltd/seafile-mc:13.0-latest

13.0-latest: Pulling from seafileltd/seafile-mc
Digest: sha256:297e0d85ba88a50dedd50b4cd412c29f090841cdfffdd3781ea086e61cd95563
Status: Image is up to date for seafileltd/seafile-mc:13.0-latest

docker.io/seafileltd/seafile-mc:13.0-latest

docker compose logs db
…

seafile-mysql | 2025-09-02 5:53:37 406 [Warning] Aborted connection 406 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 5:53:37 407 [Warning] Aborted connection 407 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 5:53:37 408 [Warning] Aborted connection 408 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 5:53:37 409 [Warning] Aborted connection 409 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 6:52:07 800 [Warning] Aborted connection 800 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 6:52:07 802 [Warning] Aborted connection 802 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 6:52:07 803 [Warning] Aborted connection 803 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 6:52:07 801 [Warning] Aborted connection 801 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 7:35:37 15 [Warning] Aborted connection 15 to db: ‘seahub_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)
seafile-mysql | 2025-09-02 7:35:37 13 [Warning] Aborted connection 13 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.23.0.5’ (Got an error reading communication packets)

1 Like
4

I have the same problem(

1 Like
5

still the same error with the latest 12.0.22. The error timestamp is every hour, around HH:07, every hour, few times (3 at least and more)

6

This error is a known issue that persists in recent versions, including 12.0.x. The specific timing you observed (every hour at HH:07) suggests it is triggered by a periodic background maintenance task or cron job within the Seafile server components.

As previously mentioned by the developers, these “Aborted connection” warnings occur because some background processes do not close their MySQL connections gracefully before exiting. While these logs can be frequent, they are considered cosmetic and do not affect the actual functionality or data integrity of your Seafile instance.

You can find more discussion and confirmation on this in the following GitHub issues:

Unless you are experiencing actual functional failures (like the web interface not loading or files failing to sync) at the exact same time as these errors, they can be safely ignored.