Author Topic: Dovecot log full of MySQL server has gone away  (Read 1844 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Dovecot log full of MySQL server has gone away
« on: December 07, 2020, 11:24:29 AM »
Hi, my dovecot log is full of the same warnings:

Quote
Dec 07 12:19:41 auth-worker(4671): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:20:41 auth-worker(4671): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:23:41 auth-worker(9017): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 57 secs)
Dec 07 12:24:41 auth-worker(9017): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:25:05 auth-worker(9017): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 24 secs)
Dec 07 12:25:05 auth-worker(9017): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 141 secs)
Dec 07 12:25:41 auth-worker(9017): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 32 secs)
Dec 07 12:26:41 auth-worker(9017): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:27:41 auth-worker(9017): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:28:41 auth-worker(11342): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:29:41 auth-worker(11342): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:30:41 auth-worker(11342): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:31:41 auth-worker(12869): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:31:59 auth-worker(12869): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 18 secs)
Dec 07 12:31:59 auth-worker(12869): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 78 secs)
Dec 07 12:32:41 auth-worker(12869): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 42 secs)
Dec 07 12:33:41 auth-worker(12869): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:34:41 auth-worker(12869): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:35:41 auth-worker(14540): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 60 secs)
Dec 07 12:36:40 auth-worker(14540): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 59 secs)
Dec 07 12:36:57 auth-worker(14540): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 17 secs)
Dec 07 13:52:50 auth-worker(18421): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 38 secs)
Dec 07 14:07:15 auth-worker(25110): Warning: mysql: Query failed, retrying: MySQL server has gone away (idled for 48 secs)

I read this is related to MySQL timeouts but to adjust it?

https://mariadb.com/kb/en/transaction-timeouts/