[Pdns-users] mysql has gone away

chayes chayes at afo.net
Tue Sep 16 20:38:01 UTC 2014


I am running pdns-recursor version 3.6
In low-usage times (approx 1.5 hours of no activity) I start seeing the
"mysql has gone away" errors and pdns becomes sluggish and unresponsive.
I searched the archives and see recommendations to increase mysql wait
times, but there is never an indication of which timeout to reset.  Here are
the options I have.  The two I would have changed (interactive_timeout and
wait_timeout) are already defaulted to eight hours. Which one should I
change to resolve the problem?  Or is there a better way?

show variables where Variable_name like '%timeout%';
+----------------------------+-------+
| Variable_name              | Value |
+----------------------------+-------+
| connect_timeout            | 10    |
| delayed_insert_timeout     | 300   |
| innodb_lock_wait_timeout   | 50    |
| innodb_rollback_on_timeout | OFF   |
| interactive_timeout        | 28800 |
| net_read_timeout           | 30    |
| net_write_timeout          | 60    |
| slave_net_timeout          | 3600  |
| table_lock_wait_timeout    | 50    |
| wait_timeout               | 28800 |
+----------------------------+-------+




--
View this message in context: http://powerdns.13854.n7.nabble.com/mysql-has-gone-away-tp10974.html
Sent from the PowerDNS mailing list archive at Nabble.com.




More information about the Pdns-users mailing list