Bug #58107 Couldn't able restore backup using mysqldump

• Submitted: 10 Nov 2010 10:40
• Modified: 12 Dec 2010 19:21
• Reporter: Anil Alpati
• Status: No Feedback
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.1.45
• OS: Any
• CPU Architecture: Any

[10 Nov 2010 10:40] Anil Alpati

Description:
Couldn't able restore backup using mysqldump.

Err : MySQL server has gone away

Backup is taken with out any issues with following variabes
 --compress , --hex

In my database some of the tables I am using BLOB. so its blocking those rows

How to repeat:
RAM 2GB

[10 Nov 2010 11:36] Sveta Smirnova

Thank you for the report.

What exact version of mysqldump you are using? This also looks like max-allowed_packet issue. Check at http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_max_allowed_pac...

[11 Nov 2010 4:23] Anil Alpati

5.1

[11 Nov 2010 10:51] Sveta Smirnova

Thank you for the feedback.

5.1 is major version and exists for years. I asked about minor version.

Have you tried to increase max_allowed_packet as described in link provided?

[11 Nov 2010 11:14] Anil Alpati

Yes even I have increase max_allowed_packet size as well

[11 Nov 2010 18:55] Sveta Smirnova

Thank you for the feedback.

So what is minor version of mysqldump? What `mysqldump --version` outputs?

[12 Nov 2010 4:37] Anil Alpati

mysql version - 5.1.45
mysqldump version - 10.13

[12 Nov 2010 19:21] Sveta Smirnova

Thank you for the feedback.

But version 5.1.45 is old. Please upgrade to current version 5.1.52 and if problem still exists send us command you use to dump, command you use to restore and output of SHOW VARIABLES LIKE 'max_allowed_packet'

[13 Dec 2010 0:01] 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".