Timeout errors with MySQL 5.7
Posted: Fri Feb 03, 2017 9:26 am
We are in the process of migrating from standalone MySQL 5.5 to the enterprise MySQL 5.7 db. We have migrated the dev and preproduction environments and the DBA started seeing the following errors repeating in the log that were no in 5.5:
2017-01-31T01:49:51.596360Z 6105558 [Note] Aborted connection 6105558 to db: 'nagios' user: 'ndoutils' host: '10.5.197.39' (Got timeout reading communication packets)
2017-01-31T01:49:51.599303Z 6105559 [Note] Aborted connection 6105559 to db: 'nagiosql' user: 'nagiosql' host: '10.5.197.39' (Got timeout reading communication packets)
2017-01-31T01:49:51.599429Z 6105557 [Note] Aborted connection 6105557 to db: 'nagiosxi' user: 'nagiosxi' host: '10.5.197.39' (Got timeout reading communication packets)
She is asking the following questions:
1. Does NAGIOSXI use connection pooling?
2. Are connections getting closed properly?
3. DO you want to check with NAGIOS support if you want to increase wait_timeout or interactive_timeout values?
2017-01-31T01:49:51.596360Z 6105558 [Note] Aborted connection 6105558 to db: 'nagios' user: 'ndoutils' host: '10.5.197.39' (Got timeout reading communication packets)
2017-01-31T01:49:51.599303Z 6105559 [Note] Aborted connection 6105559 to db: 'nagiosql' user: 'nagiosql' host: '10.5.197.39' (Got timeout reading communication packets)
2017-01-31T01:49:51.599429Z 6105557 [Note] Aborted connection 6105557 to db: 'nagiosxi' user: 'nagiosxi' host: '10.5.197.39' (Got timeout reading communication packets)
She is asking the following questions:
1. Does NAGIOSXI use connection pooling?
2. Are connections getting closed properly?
3. DO you want to check with NAGIOS support if you want to increase wait_timeout or interactive_timeout values?