PDA

View Full Version : Backup aborts - error message vague.



IanWithington
January 4th, 2008, 06:58 AM
Our backup has recently started to fail with the error message:


Fri Jan 4 02:00:02 2008: dailyrun:backup:INFO: Command used for logical backup is mysqldump --opt --extended-insert --single-transaction --create-options --default-character-set=utf8 --user="backup-user" --password="*****" --all-databases > "/home/thnas01/th-aiba-dbms/dailyrun/20080104020002/backup.sql"
Fri Jan 4 02:37:33 2008: dailyrun:backup:ERROR: mysqldump command did not succeed.
Command used is mysqldump --opt --extended-insert --single-transaction --create-options --default-character-set=utf8 --user="backup-user" --password="*****" --all-databases > "/home/thnas01/th-aiba-dbms/dailyrun/20080104020002/backup.sql"Fri Jan 4 02:37:33 2008: dailyrun:backup:INFO: backup-status=Backup failed
Fri Jan 4 02:37:33 2008: dailyrun:backup:INFO: Backup failed
Fri Jan 4 02:37:34 2008: dailyrun:backup:INFO: mailing file /home/temp/hvrnvtpEcJ

The elapsed time before it fails is variable, with a successful backup normally taking arond 51 mins.

Has anyone come across this before and what are the likely causes.

Thanks


Ian

kkg
January 7th, 2008, 12:43 AM
Our backup has recently started to fail with the error message:


Fri Jan 4 02:00:02 2008: dailyrun:backup:INFO: Command used for logical backup is mysqldump --opt --extended-insert --single-transaction --create-options --default-character-set=utf8 --user="backup-user" --password="*****" --all-databases > "/home/thnas01/th-aiba-dbms/dailyrun/20080104020002/backup.sql"
Fri Jan 4 02:37:33 2008: dailyrun:backup:ERROR: mysqldump command did not succeed.
Command used is mysqldump --opt --extended-insert --single-transaction --create-options --default-character-set=utf8 --user="backup-user" --password="*****" --all-databases > "/home/thnas01/th-aiba-dbms/dailyrun/20080104020002/backup.sql"Fri Jan 4 02:37:33 2008: dailyrun:backup:INFO: backup-status=Backup failed
Fri Jan 4 02:37:33 2008: dailyrun:backup:INFO: Backup failed
Fri Jan 4 02:37:34 2008: dailyrun:backup:INFO: mailing file /home/temp/hvrnvtpEcJ

The elapsed time before it fails is variable, with a successful backup normally taking arond 51 mins.

Has anyone come across this before and what are the likely causes.

Thanks


Ian


Could you try the following as the user you normally run the backup and post the output?
(substitute the ***** with actual password)
mysqldump --opt --extended-insert --single-transaction --create-options --default-character-set=utf8 --user="backup-user" --password="*****" --all-databases > /tmp/a.sql

--kkg

presentationmall
February 5th, 2008, 10:52 AM
Our backup has recently started to fail with the error message:


Fri Jan 4 02:00:02 2008: dailyrun:backup:INFO: Command used for logical backup is mysqldump --opt --extended-insert --single-transaction --create-options --default-character-set=utf8 --user="backup-user" --password="*****" --all-databases > "/home/thnas01/th-aiba-dbms/dailyrun/20080104020002/backup.sql"
Fri Jan 4 02:37:33 2008: dailyrun:backup:ERROR: mysqldump command did not succeed.
Command used is mysqldump --opt --extended-insert --single-transaction --create-options --default-character-set=utf8 --user="backup-user" --password="*****" --all-databases > "/home/thnas01/th-aiba-dbms/dailyrun/20080104020002/backup.sql"Fri Jan 4 02:37:33 2008: dailyrun:backup:INFO: backup-status=Backup failed
Fri Jan 4 02:37:33 2008: dailyrun:backup:INFO: Backup failed
Fri Jan 4 02:37:34 2008: dailyrun:backup:INFO: mailing file /home/temp/hvrnvtpEcJ

The elapsed time before it fails is variable, with a successful backup normally taking arond 51 mins.

Has anyone come across this before and what are the likely causes.

Thanks


Ian

Thanks for your information.

marky2coats
November 14th, 2008, 01:08 AM
Hi,

Im seeing the same thing. If I backup two smaller databases (under 1G) with the same config it works fine. As soon as I try and backup my larger db (20GB) it fails with the same error after writing 11GB of data.

Did you get this problem resvoled?

Mark.

zmanda_jacob
November 14th, 2008, 09:17 AM
Can you try again with the --verbose flag? Or set verbose=1 in your mysql-zrm.conf file? This will hopefully put some more meaningful output so we can see what the error message actually is.

paddy
November 14th, 2008, 09:24 AM
Hi,

Im seeing the same thing. If I backup two smaller databases (under 1G) with the same config it works fine. As soon as I try and backup my larger db (20GB) it fails with the same error after writing 11GB of data.

Did you get this problem resvoled?

Mark.

As Jacob said, verbose logs will help.

Are you doing local or remote backups? Are you running out of disk space? (check /tmp as well as /var/lib/mysql-zrm backup image location).

Paddy