Error executing 'FLUSH TABLES WITH READ LOCK': MySQL server has gone away
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Expired
|
Undecided
|
Unassigned |
Bug Description
Using percona-
Trying to use innobackupex with this commandline, but it never completes:
$ innobackupex-1.5.1 --user=root --password=XXXXXX --slave-info --defaults-
Last lines I get:
>> log scanned up to (875342718308)
xtrabackup: Creating suspend file '/tmp/xtrabacku
>> 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: Error:
Error executing 'FLUSH TABLES WITH READ LOCK': DBD::mysql::db do failed: MySQL server has gone away at /usr/bin/
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,
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. /www.percona. com/downloads/ XtraBackup/
https:/