Bug #84612 Provide more verbose logging on connection failures and aborts
Submitted: 23 Jan 2017 14:15
Reporter: Sveta Smirnova (OCA) Email Updates:
Status: Open Impact on me:
Category:MySQL Server: Logging Severity:S4 (Feature request)
Version:5.5, 5.6, 5.7, 8.0 OS:Any
Assigned to: CPU Architecture:Any

[23 Jan 2017 14:15] Sveta Smirnova
Currently, even with log_wanrings set to 2 (or error_log_verbosity set to 3), it is hard to find out why connection was closed. Was it during connection initialization? Because it was closed after timeout reached? Some other error occurred? For most cases only error like "2017-01-20T21:44:52.301177Z 5 [Note] Aborted connection 5 to db: 'test' user: 'root' host: 'localhost' (Got timeout reading communication packets)" printed.

How to repeat:
Imitate wait_timeout error, then check message in the log.

Suggested fix:
Provide more details on errors when it possible.

While we can check Aborted_connects and Aborted_clients variables after server was running long time it could be hard to identify what causes messages in the log at the specific period.