Bug #68911 mysqldump Error 2013: Lost connection to MySQL server during query when dumping
Submitted: 10 Apr 2013 0:52 Modified: 10 May 2013 5:19
Reporter: 舒揚 陳 Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Backup Severity:S3 (Non-critical)
Version:5.1.4 OS:Linux (RHEL 5.1)
Assigned to: CPU Architecture:Any

[10 Apr 2013 0:52] 舒揚 陳
Description:
When we backup mysql database by mysqldump, error occures sometimes.

The client error message is "Error 2013: Lost connection to MySQL server during query when dumping table `t_ctf_prc` at row: 90741".

There is also a database error written in err-log file, it is "130407  4:35:04 [Warning] Aborted connection 12290 to db: 'SSN01P' user: 'SSN001' host: '146.215.107.70' (Got timeout writing communication packets)".

I think something internal error occures in mysqldump running term.
But I can`t get error details as Oracle.

The writing timeout means the network between server and client is too weakness?
(default net_write_timeout = 60)

How to repeat:
If I set the net_write_write_timeout = 1, I could repeat it at client mysqldump.
But the server err-log reports the "Got timeout reading ......".
[10 Apr 2013 5:19] MySQL Verification Team
Thank you for the report.

But version 5.1.4 is very old and many bugs were fixed since. Please upgrade to current version 5.1.68, try with it and inform us if problem still exists and provide: 

- full server error log file also.
- output of show global variables like '%timeout%'; 

Workaround: try to change max_allowed_packet to largest value and see if it helps.
[11 May 2013 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".