Comments on: MySQL “Got an error reading communication packet”

By: 1karu5

1karu5 — Wed, 24 Jun 2020 22:50:07 +0000

this is the first time that read about the “TIME_WAIT” problem… my god !!! TIME_WAIT is normal !!! it informs about the correct CLOSE of a Network Connection. Maybe you are put a peace of fruit…

By: madhu

madhu — Mon, 17 Jun 2019 13:06:32 +0000

Hi All,

i facing this error “Got timeout/error reading communication packets.”
Aborted connection 357093 to db: ‘’user: ‘root’ host: ‘cloudsqlproxy~0.0.0.0’ (Got timeout/error reading communication packets)

I tried multiple options by increasing the max_allowed_packet value from 100MB to 1GB and adding new variables in mysql db.

max_allowed_packet from 100MB to 1GB(1073741824)
wait_timeout 86400 (wait_timeout with default value =28800(8hrs to 24hrs)
interactive_timeout 86400(default value =28800)
net_read_timeout 28800(default value =30)
net_write_timeout 28800(default value =60)
max_connections =400

Still the issue exists.

please help on this.

Thanks,
madhu Reddy

By: guest

guest — Thu, 14 Dec 2017 15:47:33 +0000

Another trial reason I once met is innodb_buffer_pool_size set to 8 mb (when queries seemed to return much bigger data)

By: dennis gao

dennis gao — Mon, 26 Jun 2017 08:11:59 +0000

Is there any way to let server not do the log for Aborted connection?

By: idrissa

idrissa — Fri, 24 Feb 2017 08:42:26 +0000

Thanks for the information

By: Richard vK

Richard vK — Thu, 01 Sep 2016 13:00:40 +0000

I found lots of these going through my database, and spend a lot of time trying to adjust both application/apache/freeradius and mysql parameters, all to no avail.

It turned out the timeout setting in haproxy (which sits between my cluster and all applications) had a 15 second timeout, which was shorter than all other timeouts. This makes sense in hindsight: its expected that apache, freeradius etc would cleanly close their timed out or expired db connections, however if something in the middle (ie haproxy) kills it, it would not be a clean disconnect, and you would expect this type of error in the logs.

By: Sligcm

Sligcm — Tue, 16 Aug 2016 03:21:45 +0000

Thanks for the valuable information.

By: ranvijay mehta

ranvijay mehta — Thu, 11 Aug 2016 20:13:50 +0000

Thanks Inrfan for the valuable information.

By: Aftab Khan

Aftab Khan — Tue, 17 May 2016 15:58:35 +0000

Another nice blog!

Just to add few cents, starting from MySQL 5.7.2 debugging connection has been made little easier:

a) You can get more information about the lost connections by starting mysqld with the “log_error_verbosity” system variable set to 3

b) The ID included in error log messages is that of the thread within mysqld responsible for writing the message. This will help identify which part of the server produced the message, and is consistent with general query log and slow query log messages which include the connection thread ID. Before MySQL 5.7.2, the ID in error log messages is that of the mysqld process ID.