Bug #24903 timeout in mysqld.conf causes Got timeout reading communication packets
Submitted: 8 Dec 2006 10:23 Modified: 24 Jun 2009 9:20
Reporter: Arkadiusz Miskiewicz (Basic Quality Contributor) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version:5.0.27 OS:Linux (Linux)
Assigned to: CPU Architecture:Any
Tags: qc
Triage: Needs Triage: D5 (Feature request)

[8 Dec 2006 10:23] Arkadiusz Miskiewicz
Description:
My settings are:

log-warnings = 2
log-error  = /var/log/mysql/error
set-variable = connect_timeout=30
set-variable = interactive_timeout=180
set-variable = wait_timeout=180

I have some connections haning around and sleeping for long time. When that time reaches 180 server disconnects the client. 

That's fine but why it's logging for each such terminated connection:
061208 11:21:36 [Warning] Aborted connection 951 to db: 'xyz' user: 'abc' host: 'some.host.org' (Got timeout reading communication packets)

?

How to repeat:
Use settings I've provided and connect for long time without issuing any sql commands.
[8 Dec 2006 13:58] Hartmut Holzgraefe
this is the expected behavior, i agree though that for this 
special case of connection termination a more meaningfull
error message might make sense here.

Verified and changed to "feature request"
[8 Dec 2006 14:38] Arkadiusz Miskiewicz
IMO there should be no error message at all since terminating such connection is not a error but desired behaviour (initiated by setting timeout values...)
[24 Jun 2009 9:20] Sveta Smirnova
Thank you for the reasonable feature request, although I disagree with "no error" Meaningful error in case if log-warnings set to 2 is better.