-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 17.1.1, 18.0.0
-
Fix Version/s: Meridian-2015.1.2, Meridian-2016.1.2, 18.0.1
-
Component/s: Data Collection - JDBC
-
Security Level: Default (Default Security Scheme)
-
Labels:
When using the JdbcCollector for a MySQL 5.7 server, I saw the following notes in mysql.log:
2016-04-14T13:05:44.692827Z 77 [Note] Aborted connection 77 to db:'information_schema' user: 'opennms' host: '10.1.15.17' (Got an error reading communication packets) 2016-04-14T13:05:44.692829Z 73 [Note] Aborted connection 73 to db:'information_schema' user: 'opennms' host: '10.1.15.17' (Got an error reading communication packets) 2016-04-14T13:05:44.692966Z 89 [Note] Aborted connection 89 to db:'information_schema' user: 'opennms' host: '10.1.15.17' (Got an error reading communication packets) 2016-04-14T13:05:44.693006Z 95 [Note] Aborted connection 95 to db:'information_schema' user: 'opennms' host: '10.1.15.17' (Got an error reading communication packets)
These lines occur on every datacollection interval and stil occur if Polling and Provisioning were disabled. When I disable Collectd I can't see these lines anymore. So there seems to be an issue with the connection handling in JdbcCollector.
I did some further investigation with wireshark. Per collected value a new JDBC connection was created, but only for a few connections I saw a MySQL close at the end before TCP FIN.
