Error executing 'FLUSH TABLES WITH READ LOCK': MySQL server has gone away

Bug #1470716 reported by Patrice Levesque
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Expired
Undecided
Unassigned

Bug Description

Using percona-xtrabackup-21-2.1.9-746.rhel6.x86_64 under CentOS6.

Trying to use innobackupex with this commandline, but it never completes:

$ innobackupex-1.5.1 --user=root --password=XXXXXX --slave-info --defaults-file=/etc/my.cnf --stream=tar /tmp/ | nc fileserver 6789

Last lines I get:

>> log scanned up to (875342718308)
xtrabackup: Creating suspend file '/tmp/xtrabackup_suspended_2' with pid '26055'
>> log scanned up to (875342718308)

150702 00:47:52 innobackupex-1.5.1: Continuing after ibbackup has suspended
150702 00:47:52 innobackupex-1.5.1: Starting to lock all tables...
DBD::mysql::db do failed: MySQL server has gone away at /usr/bin/innobackupex-1.5.1 line 3009.
innobackupex-1.5.1: Error:
Error executing 'FLUSH TABLES WITH READ LOCK': DBD::mysql::db do failed: MySQL server has gone away at /usr/bin/innobackupex-1.5.1 line 3009.
150702 00:47:52 innobackupex-1.5.1: Waiting for ibbackup (pid=26055) to finish

/var/lib/mysql is about 200GB. That's about the same amount of data that is transmitted through netcat.

Everything takes a couple of hours to complete.

Is there a MySQL ping somewhere I can insert in innobackupex to avoid this? Or any other workaround?

Thanks,

Revision history for this message
Nilnandan Joshi (nilnandan-joshi) wrote :

Hi,

Can you please provide the error log of MySQL server? Also, you are using very old version of Xtrabackup. Can you please try to use the latest version and check if you are getting the same error? please provide MySQL version too.
https://www.percona.com/downloads/XtraBackup/

Changed in percona-xtrabackup:
status: New → Incomplete
Revision history for this message
Patrice Levesque (sysadmin-9) wrote :

Upgrading to percona-xtrabackup-2.2.11-1.el6.x86_64 did the trick. Thanks for your time and for your answer.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

Changed in percona-xtrabackup:
status: Incomplete → Expired
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1336

Revision history for this message
Sreeraj R (sree0001) wrote :

I am facing this issue in one of the servers. Others are working fine with percona backup

How to resolve this issue ?

> log scanned up to (7142210953)
xtrabackup: Creating suspend file '/data/backup/aeplhr/2018-01-30_01-00-03/xtrabackup_suspended_2' with pid '4949'
>> log scanned up to (7142210953)

180130 01:02:40 innobackupex-1.5.1: Continuing after ibbackup has suspended
180130 01:02:40 innobackupex-1.5.1: Starting to lock all tables...
DBD::mysql::db do failed: Got an error writing communication packets at /usr/local/percona/bin/innobackupex-1.5.1 line 3009.
innobackupex-1.5.1: Error:
Error executing 'FLUSH TABLES WITH READ LOCK': DBD::mysql::db do failed: Got an error writing communication packets at /usr/local/percona/bin/innobackupex-1.5.1 line 3009.
180130 01:02:40 innobackupex-1.5.1: Waiting for ibbackup (pid=4949) to finish

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.