XtraBackup exits with warning, status > 0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.1 |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.2 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
I am utilizing the following scripts for my backups of PXC:
https:/
- xbackup.sh
- xbackup-run.sh
Essentially, the backup is reporting following warning during the backup: "InnoDB: Warning: allocated tablespace 1513, old maximum was 9"
xbackup-run.sh is a wrapper script for xbackup.sh, and on exit of xbackup.sh, the exit status != 0 because of the warnings. I get an email that the backup has failed, even though it has successfully completed.
Percona rpm versions:
Percona-
percona-
percona-
Percona-
Percona-
Percona-
Percona-
This part of xbackup-run.sh is what causes the email alerting to a failed backup:
if [ "${PIPESTATUS[0]}" -ne 0 ]; then
(echo "Subject: ERROR: MySQL Backup failed on `hostname`";
cat ${WORK_
if [ -f $LOG_FILE ]; then cat $LOG_FILE; fi;
) | /usr/sbin/sendmail -O NoRecipientActi
else
(echo "Subject: MySQL Backup complete on `hostname`";
cat ${WORK_
) | /usr/sbin/sendmail -O NoRecipientActi
fi
Pertinent portion of xtrabackup log (if you need more, please advise):
2014-01-21_01_01_02 xbackup INFO: Backing up with: /usr/bin/
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://
140121 01:01:02 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:
140121 01:01:02 innobackupex: Connected to MySQL server
140121 01:01:02 innobackupex: Executing a version check against the server...
140121 01:01:02 innobackupex: Done.
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
innobackupex: Using mysql server version 5.5.34-55-log
innobackupex: Created backup directory /operation/
140121 01:01:02 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-
innobackupex: Waiting for ibbackup (pid=11463) to suspend
innobackupex: Suspend file '/operation/
xtrabackup_55 version 2.1.6 for Percona Server 5.5.31 Linux (x86_64) (revision id: 702)
incremental backup from 19907164778 is enabled.
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using O_DIRECT
>> log scanned up to (19930927576)
140121 1:01:02 InnoDB: Warning: allocated tablespace 1513, old maximum was 9
>> log scanned up to (19930927640)
....
....
<near end of log>
....
140121 01:04:09 innobackupex: completed OK!
2014-01-21_01_04_09 xbackup INFO: Apply log finished: Tue Jan 21 01:04:09 EST 2014
2014-01-21_01_04_10 xbackup INFO: Cleaning up previous backup files:
2014-01-21_01_04_10 xbackup ... done
2014-01-21_01_04_10 xbackup INFO: Backup job finished: Tue Jan 21 01:04:10 EST 2014
2014-01-21_01_04_10 xbackup INFO: Backup size: 177M
2014-01-21_01_04_10 xbackup INFO: Remaining space available on backup device: 14T
2014-01-21_01_04_10 xbackup INFO: Logfile: /operation/
2014-01-21_01_04_10 xbackup INFO: Last full backup fully prepared (including incrementals): /operation/
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 1186 lines (+192/-121)5 files modifiedpatches/innodb51.patch (+36/-22)
patches/innodb55.patch (+35/-21)
patches/innodb56.patch (+48/-35)
patches/xtradb51.patch (+36/-22)
patches/xtradb55.patch (+37/-21)
- Alexey Kopytov (community): Approve
-
Diff: 16 lines (+0/-6)1 file modifiedstorage/innobase/fil/fil0fil.cc (+0/-6)
tags: | added: i38702 |
Percona support has stated that this warning is benign and safe to ignore, and that it is not creating an invalid condition in XtraBackup. Therefore, the warning should be removed so that innobackupex does not return an exit status greater than 0.