mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #605] Error in Mariadb logs, What does it mean? #401
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#401
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BobWs on GitHub (Sep 6, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/605
Hi,
Any idea what this error message mean:
I'm getting it with the bitwardenrs-myslq server and mariadb latest
@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.
@BobWs commented on GitHub (Sep 7, 2019):
Thanks! Look indeed similar. I will give it a try, restarting the mariadb database.
@BobWs commented on GitHub (Oct 16, 2019):
Error messages still there, they disappear when restarting mariadb but after a while it returns.
@dearekaelle commented on GitHub (Apr 29, 2020):
after migrating my sqlite to mariadb, I am having the same issue.
@BobWs commented on GitHub (May 1, 2020):
The Error is still there. Restating doesn't it just a short term solution
@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.
@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.
@BobWs commented on GitHub (May 14, 2020):
No issues as far as I can see. Just a warning in the log
@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
@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 (Oct 3, 2020):
Please reopen if this persist
@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 :)
@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
@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.
@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.