Error in Mariadb logs, What does it mean? #402

Closed
opened 2025-11-07 06:35:09 -06:00 by GiteaMirror · 15 comments
Owner

Originally created by @BobWs on GitHub (Sep 6, 2019).

Hi,

Any idea what this error message mean:

`2019-09-05 22:35:18 42 [Warning] Aborted connection 42 to db: 'bitwarden' user: 'bitwarden' host: '172.17.0.4' (Got an error reading communication packets) stderr

I'm getting it with the bitwardenrs-myslq server and mariadb latest

Originally created by @BobWs on GitHub (Sep 6, 2019). Hi, Any idea what this error message mean: `2019-09-05 22:35:18 42 [Warning] Aborted connection 42 to db: 'bitwarden' user: 'bitwarden' host: '172.17.0.4' (Got an error reading communication packets) | stderr -- | -- I'm getting it with the bitwardenrs-myslq server and mariadb latest
Author
Owner

@mikey242 commented on GitHub (Sep 7, 2019):

I'm not sure if this is related but I get a similar error when restarting my server:

Aborted connection 1359 to db: 'bitwarden' user: 'bitwarden' host: '172.30.0.3' (Got timeout reading communication packets)

It's easily remedied by just restarting the mysql database.

@mikey242 commented on GitHub (Sep 7, 2019): I'm not sure if this is related but I get a similar error when restarting my server: `Aborted connection 1359 to db: 'bitwarden' user: 'bitwarden' host: '172.30.0.3' (Got timeout reading communication packets)` It's easily remedied by just restarting the mysql database.
Author
Owner

@BobWs commented on GitHub (Sep 7, 2019):

I'm not sure if this is related but I get a similar error when restarting my server:

Aborted connection 1359 to db: 'bitwarden' user: 'bitwarden' host: '172.30.0.3' (Got timeout reading communication packets)

It's easily remedied by just restarting the mysql database.

Thanks! Look indeed similar. I will give it a try, restarting the mariadb database.

@BobWs commented on GitHub (Sep 7, 2019): > I'm not sure if this is related but I get a similar error when restarting my server: > > `Aborted connection 1359 to db: 'bitwarden' user: 'bitwarden' host: '172.30.0.3' (Got timeout reading communication packets)` > > It's easily remedied by just restarting the mysql database. Thanks! Look indeed similar. I will give it a try, restarting the mariadb database.
Author
Owner

@BobWs commented on GitHub (Oct 16, 2019):

Error messages still there, they disappear when restarting mariadb but after a while it returns.

@BobWs commented on GitHub (Oct 16, 2019): Error messages still there, they disappear when restarting mariadb but after a while it returns.
Author
Owner

@dearekaelle commented on GitHub (Apr 29, 2020):

after migrating my sqlite to mariadb, I am having the same issue.

@dearekaelle commented on GitHub (Apr 29, 2020): after migrating my sqlite to mariadb, I am having the same issue.
Author
Owner

@BobWs commented on GitHub (May 1, 2020):

The Error is still there. Restating doesn't it just a short term solution

@BobWs commented on GitHub (May 1, 2020): The Error is still there. Restating doesn't it just a short term solution
Author
Owner

@dani-garcia commented on GitHub (May 13, 2020):

Does this cause any problems? It seems only a warning according to the message, maybe diesel doesn't close the connections correctly before dropping them.

@dani-garcia commented on GitHub (May 13, 2020): Does this cause any problems? It seems only a warning according to the message, maybe diesel doesn't close the connections correctly before dropping them.
Author
Owner

@dearekaelle commented on GitHub (May 14, 2020):

I have not noticed any functional issues or otherwise. bitwarden_rs with all the apps seems to be working well despite the warnings in the db logs.

@dearekaelle commented on GitHub (May 14, 2020): I have not noticed any functional issues or otherwise. bitwarden_rs with all the apps seems to be working well despite the warnings in the db logs.
Author
Owner

@BobWs commented on GitHub (May 14, 2020):

No issues as far as I can see. Just a warning in the log

@BobWs commented on GitHub (May 14, 2020): No issues as far as I can see. Just a warning in the log
Author
Owner

@random-issue commented on GitHub (May 14, 2020):

From the bitwarden_rs perspective it looks like it's performing just fine. But it does look like whatever is managing db connections is closing them incorrectly.
I haven't had much time to dig into where in bitwarden_rs code this is taking place, if it is diesel, but some information I found (some are older than others, but it seems the first point from the first article would match):
https://www.percona.com/blog/2016/05/16/mysql-got-an-error-reading-communication-packet-errors/
https://stackoverflow.com/q/23689803
https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html

@random-issue commented on GitHub (May 14, 2020): From the bitwarden_rs perspective it looks like it's performing just fine. But it does look like whatever is managing db connections is closing them incorrectly. I haven't had much time to dig into where in bitwarden_rs code this is taking place, if it is diesel, but some information I found (some are older than others, but it seems the first point from the first article would match): https://www.percona.com/blog/2016/05/16/mysql-got-an-error-reading-communication-packet-errors/ https://stackoverflow.com/q/23689803 https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html
Author
Owner

@BlackDex commented on GitHub (Sep 22, 2020):

It would also be a good check to see if there are many sleeping connections for example.
It could also very well be an issue with the network (docker overlay/proxy).
Or some mysql/mariadb tweaks which could be done to tweak this.

@BlackDex commented on GitHub (Sep 22, 2020): It would also be a good check to see if there are many sleeping connections for example. It could also very well be an issue with the network (docker overlay/proxy). Or some mysql/mariadb tweaks which could be done to tweak this.
Author
Owner

@BlackDex commented on GitHub (Oct 3, 2020):

Please reopen if this persist

@BlackDex commented on GitHub (Oct 3, 2020): Please reopen if this persist
Author
Owner

@andreymal commented on GitHub (Dec 22, 2021):

@BlackDex @dani-garcia it's still present with 1.23.1

Even if everything works fine, these messages are a little annoying because they are red :)

vaultwarden-warn

@andreymal commented on GitHub (Dec 22, 2021): @BlackDex @dani-garcia it's still present with 1.23.1 Even if everything works fine, these messages are a little annoying because they are red :) ![vaultwarden-warn](https://user-images.githubusercontent.com/3236464/147090930-c8f1ea25-0993-4fdc-9911-b4b07b7018a7.png)
Author
Owner

@fgionghi commented on GitHub (Jun 8, 2023):

I have the same error, I'm not able to solve this and it's affecting vaultwarden functionality: I can not restore a db backup, I cannot register new users, but I can create a new item correctly.
I tried to set some parameters to high values to testing:
--max_connections=1000
--interactive-timeout=31536000
--wait-timeout=31536000
and in the config file:
[mysqld]
max_allowed_packet=800M
innodb_log_buffer_size = 60M
innodb_log_file_size = 5000M

Keep having the same error message (2023-06-07 12:57:15 2517 [Warning] Aborted connection 2517 to db: 'vaultwarden' user: 'vaultwarden' host: '10.193.4.80' (Got an error reading communication packets))

I'm on kuberntes and using bitnami/mariadb:10.11.2-debian-11-r9 as db and vaultwarden/server:1.28.1

@fgionghi commented on GitHub (Jun 8, 2023): I have the same error, I'm not able to solve this and it's affecting vaultwarden functionality: I can not restore a db backup, I cannot register new users, but I can create a new item correctly. I tried to set some parameters to high values to testing: --max_connections=1000 --interactive-timeout=31536000 --wait-timeout=31536000 and in the config file: [mysqld] max_allowed_packet=800M innodb_log_buffer_size = 60M innodb_log_file_size = 5000M Keep having the same error message (`2023-06-07 12:57:15 2517 [Warning] Aborted connection 2517 to db: 'vaultwarden' user: 'vaultwarden' host: '10.193.4.80' (Got an error reading communication packets)`) I'm on kuberntes and using bitnami/mariadb:10.11.2-debian-11-r9 as db and vaultwarden/server:1.28.1
Author
Owner

@KhangCoffee commented on GitHub (Jul 30, 2024):

I also had the same problem with zabbix when changing the path from /var/lib/mysql to /home/lib/mysql. If I switch back to /var/lib/mysql it works fine again.
1q

@KhangCoffee commented on GitHub (Jul 30, 2024): I also had the same problem with zabbix when changing the path from /var/lib/mysql to /home/lib/mysql. If I switch back to /var/lib/mysql it works fine again. ![1q](https://github.com/user-attachments/assets/0f21fefc-8a06-46aa-853e-3eaf993f3c3c)
Author
Owner

@BlackDex commented on GitHub (Jul 30, 2024):

That might be either systemd which has some path protections in the services. Or other auditing tools like SELinux or apparmor.

@BlackDex commented on GitHub (Jul 30, 2024): That might be either systemd which has some path protections in the services. Or other auditing tools like SELinux or apparmor.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#402