[Note] Aborted connection ... (Got an error reading communication packets)

[Fabio Cavassini]

Hi, 

I've found an error in my MySQL ( MySQL 2nd Gen 5.7 ondb-n1-standard-1 ) error log and a pattern, this "Aborted connection" error always appears before this insert: "INSERT INTO mysql.heartbeat(id, master_time)..."

A  2018-05-17T18:43:29.415379Z	638401 Query	INSERT INTO mysql.heartbeat(id, master_time) 
E  2018-05-17T18:43:29.191513Z 638442 [Note] Aborted connection 638442 to db: 'xxxxxxxxx' user: 'root' host: 'cloudsqlproxy~74.125.182.17' (Got an error reading communication packets) 

A  2018-05-17T18:43:19.358269Z	638401 Query	INSERT INTO mysql.heartbeat(id, master_time) 
E  2018-05-17T18:43:19.308447Z 638440 [Note] Aborted connection 638440 to db: 'xxxxxxxxx' user: 'root' host: 'cloudsqlproxy~173.194.90.33' (Got an error reading communication packets)

My database has high availability enabled, and for what I had seen, that insert corresponds to Percora Toolkit  / Monitor MySQL replication delay (https://www.percona.com/doc/percona-toolkit/LATEST/pt-heartbeat.html)

Maybe it's related to this Cloud SQL Proxy too: https://github.com/GoogleCloudPlatform/cloudsql-proxy/issues/126

I think the connection that executes that insert is not properly being managed.

Thanks

Fabio

[Fady (Google Cloud Platform)]

Hello Fabio,

The above message is triggered when an existing connection is terminated improperly, which may look erroneous but is actually perfectly normal. Aborted connections happen because of unclean closure of connection or networking problem between the server and the client, but not because of the server.

[Fabio Cavassini]

Thanks Fady, we checked and we had some functions that were improperly destroying the connection, thank you!!!