haiwen / seafile

High performance file syncing and sharing, with also Markdown WYSIWYG editing, Wiki, file label and other knowledge management features.
http://seafile.com/
Other
12.4k stars 1.55k forks source link

Mariadb Warning #2508

Open fearlessxjdx opened 3 years ago

fearlessxjdx commented 3 years ago
[Warning] Aborted connection 70 to db: 'seafile_db' user: 'seafile' host: '172.21.21.21' (Got an error reading communication packets)

Does this matter? How to fix this? mariadb:10.5

killing commented 3 years ago

I think this is just a network error.

fearlessxjdx commented 2 years ago

I think this is just a network error.

But I'm running with docker, the IP address 172.21.21.21 is actually the local machine.

Before I upgraded to 9.0, there were none warnings.

aymenSo commented 1 year ago

I have the same warning: 2023-10-27 9:46:46 3358 [Warning] Aborted connection 3358 to db: 'seafile_db' user: 'seafile' host: '172.27.0.2' (Got an error reading communication packets) Seafile pro in docker mariaDB v10.7 and Seafile pro v9.0.5

RaidOpe commented 12 months ago

same in mine

2023-11-26 12:06:13 54 [Warning] Aborted connection 54 to db: 'unconnected' user: 'seafile' host: '192.168.240.4' (Got an error reading communication packets) 2023-11-26 12:06:20 57 [Warning] Aborted connection 57 to db: 'seahub_db' user: 'seafile' host: '192.168.240.4' (Got an error reading communication packets)

and whatever I set SEAFILE_ADMIN_EMAIL SEAFILE_ADMIN_PASSWORD , then popping up CSRF verification failed. Request aborted.

heartnn commented 11 months ago

same in mine

2023-11-26 12:06:13 54 [Warning] Aborted connection 54 to db: 'unconnected' user: 'seafile' host: '192.168.240.4' (Got an error reading communication packets) 2023-11-26 12:06:20 57 [Warning] Aborted connection 57 to db: 'seahub_db' user: 'seafile' host: '192.168.240.4' (Got an error reading communication packets)

and whatever I set SEAFILE_ADMIN_EMAIL SEAFILE_ADMIN_PASSWORD , then popping up CSRF verification failed. Request aborted.

https://manual.seafile.com/config/seahub_settings_py/

Security settings

# For security consideration, please set to match the host/domain of your site, e.g., ALLOWED_HOSTS = ['.example.com'].
# Please refer https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts for details.
ALLOWED_HOSTS = ['.myseafile.com']

# Whether to use a secure cookie for the CSRF cookie
# https://docs.djangoproject.com/en/3.2/ref/settings/#csrf-cookie-secure
CSRF_COOKIE_SECURE = True

# The value of the SameSite flag on the CSRF cookie
# https://docs.djangoproject.com/en/3.2/ref/settings/#csrf-cookie-samesite
CSRF_COOKIE_SAMESITE = 'Strict'

# https://docs.djangoproject.com/en/3.2/ref/settings/#csrf-trusted-origins
CSRF_TRUSTED_ORIGINS = ['https://www.myseafile.com']
Moosbueffel commented 4 months ago

I have the same problem just installed the current docker "seafile PE 11.0".

Is there no solution in the meantime? Some other things don't work in Browser like open docs, or upload files. Perhaps this is the reason?

2024-07-24 20:57:44 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'root' host: '172.24.0.4' (Got an error reading communication packets)

2024-07-24 20:58:22 12 [Warning] Aborted connection 12 to db: 'seahub_db' user: 'seafile' host: '172.24.0.4' (Got an error reading communication packets)
seafile-mysql | 2024-07-24 20:58:22 16 [Warning] Aborted connection 16 to db: 'seahub_db' user: 'seafile' host: '172.24.0.4' (Got an error reading communication packets)
^CGracefully stopping... (press Ctrl+C again to force)

grafik

hydrandt commented 2 months ago

I also see these errors in the log. Moreover, while doing garbage collection (docker), I get several times (seems to be same time as the warning message in mysql container:

../../common/seaf-db.c(907): Failed to execute sql REPLACE INTO RepoValidSince (repo_id, timestamp) VALUES ('317520f9-0232-4071-bdae-fbed301d22e9', 1717664255): Lost connection to server during query

Docker-compose deployment.

fcnjd commented 1 month ago

Same is for me with a freshly setup docker-compose deployment. Seafile 11, MariaDB 10. @killing Can you please re-open this? As a lot of people obviosly do have this problem, this should get seriosly discussed somewhere.

D1reW0lf commented 1 month ago

Hi all.

Just to add my "me too" on this. Just installed Seafile 11.0.15 professional under docker and my log is filled with_

seafile-mysql | 2024-10-23 13:56:35 481 [Warning] Aborted connection 481 to db: 'seafile_db' user: 'seafile' host: '172.23.0.8' (Got an error reading communication packets)

https://github.com/haiwen/seafile/issues/2508#issuecomment-1835479482 I already have all the settings in here but the problem still remains.

I don't know if that's why I have so many aborted downloads with a "bad request" error.

fengwang commented 2 weeks ago

Happens again... Would @fearlessxjdx please reopen this issue?

I brought everything up using a docker-compose.yml, worked fine in the first place, and then came across to this issue.

The db log:

2024-11-06 11:00:28 5 [Warning] Aborted connection 5 to db: 'ccnet_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 4 [Warning] Aborted connection 4 to db: 'seafile_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 136 [Warning] Aborted connection 136 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 117 [Warning] Aborted connection 117 to db: 'seafile_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 135 [Warning] Aborted connection 135 to db: 'seafile_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 98 [Warning] Aborted connection 98 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 134 [Warning] Aborted connection 134 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 100 [Warning] Aborted connection 100 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 118 [Warning] Aborted connection 118 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 11 [Warning] Aborted connection 11 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 7 [Warning] Aborted connection 7 to db: 'seafile_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 115 [Warning] Aborted connection 115 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 116 [Warning] Aborted connection 116 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 8 [Warning] Aborted connection 8 to db: 'seafile_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 6 [Warning] Aborted connection 6 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:28 99 [Warning] Aborted connection 99 to db: 'seafile_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:33 152 [Warning] Aborted connection 152 to db: 'seafile_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:36 156 [Warning] Aborted connection 156 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)
2024-11-06 11:00:36 158 [Warning] Aborted connection 158 to db: 'seahub_db' user: 'seafile' host: '192.168.64.2' (Got an error reading communication packets)

The seafile/seahub log:


Starting seahub at port 8000 ...
Error:Seahub failed to start.
Please try to run "./seahub.sh start" again
waiting for mysql server to be ready: %s (2003, "Can't connect to MySQL server on 'db' ([Errno 111] Connection refused)")
Traceback (most recent call last):
  File "/scripts/start.py", line 95, in <module>
    main()
  File "/scripts/start.py", line 81, in main
    call('{} start'.format(get_script('seahub.sh')))
  File "/scripts/utils.py", line 70, in call
    return subprocess.check_call(*a, **kw)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/seafile/seafile-server-11.0.5/seahub.sh start' returned non-zero exit status 1.
ThatCoffeeGuy commented 2 weeks ago

Same, completely broke seafile.

seafile-mysql | 2024-11-06 13:12:08 0 [Note] Server socket created on IP: '0.0.0.0'. seafile-mysql | 2024-11-06 13:12:08 0 [Note] Server socket created on IP: '::'. seafile-mysql | 2024-11-06 13:12:09 0 [Note] mariadbd: ready for connections. seafile-mysql | Version: '10.11.9-MariaDB-ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution seafile-mysql | 2024-11-06 13:12:09 0 [Note] InnoDB: Buffer pool(s) load completed at 241106 13:12:09 seafile-mysql | 2024-11-06 13:12:17 6 [Warning] Aborted connection 6 to db: 'seahub_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets) seafile-mysql | 2024-11-06 16:10:59 24 [Warning] Aborted connection 24 to db: 'seafile_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets) seafile-mysql | 2024-11-06 16:10:59 48 [Warning] Aborted connection 48 to db: 'seahub_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets) seafile-mysql | 2024-11-06 16:10:59 49 [Warning] Aborted connection 49 to db: 'seahub_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets) seafile-mysql | 2024-11-06 16:10:59 47 [Warning] Aborted connection 47 to db: 'seahub_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets) seafile-mysql | 2024-11-06 16:10:59 31 [Warning] Aborted connection 31 to db: 'seafile_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets) seafile-mysql | 2024-11-06 16:10:59 4 [Warning] Aborted connection 4 to db: 'seafile_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets) seafile-mysql | 2024-11-06 16:10:59 5 [Warning] Aborted connection 5 to db: 'ccnet_db' user: 'seafile' host: '172.19.0.4' (Got an error reading communication packets)

faceslog commented 2 weeks ago

Same issue as everyone, I managed to make a stupid script that restart the seafile docker when it fails after some time but it's not practical ...

Error in mariadb container: 2024-10-29 22:08:21 17 [Warning] Aborted connection 17 to db: 'seahub_db' user: 'seafile' host: '172.22.0.4' (Got an error reading communication packets)

Issue should not be closed

SkywalkerSpace commented 1 week ago

For troubleshooting, when there were a lot of [Warning] Aborted connection ..., please send the seahub.log, seafile.log, seafevents.log at that moment.

By the way, please make sure docker is the latest version.