XtraBackup exits with warning, status > 0

Bug #1271956 reported by Scott Haas on 2014-01-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Sergei Glushchenko
Sergei Glushchenko
Sergei Glushchenko

Bug Description

I am utilizing the following scripts for my backups of PXC:

   - 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:

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_DIR}/${CURDATE}-info.log;
    if [ -f $LOG_FILE ]; then cat $LOG_FILE; fi;
    ) | /usr/sbin/sendmail -O NoRecipientAction=add-to -f${MAIL_FROM} ${MAIL_TO_ERROR}
  (echo "Subject: MySQL Backup complete on `hostname`";
    cat ${WORK_DIR}/${CURDATE}-info.log;
  ) | /usr/sbin/sendmail -O NoRecipientAction=add-to -f${MAIL_FROM} ${MAIL_TO}

Pertinent portion of xtrabackup log (if you need more, please advise):

2014-01-21_01_01_02 xbackup INFO: Backing up with: /usr/bin/innobackupex --defaults-file=/etc/my.cnf --galera-info --no-timestamp --incremental /operation/working/bkps/2014-01-21_01_01_02 --incremental-basedir /operation/working/bkps/2014-01-20_11_48_01

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:

140121 01:01:02 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_file=/etc/my.cnf;mysql_read_default_group=xtrabackup' (using password: NO).
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/working/bkps/2014-01-21_01_01_02

140121 01:01:02 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-file="/etc/my.cnf" --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/operation/working/bkps/2014-01-21_01_01_02 --tmpdir=/tmp --incremental-basedir='/operation/working/bkps/2014-01-20_11_48_01'
innobackupex: Waiting for ibbackup (pid=11463) to suspend
innobackupex: Suspend file '/operation/working/bkps/2014-01-21_01_01_02/xtrabackup_suspended_2'

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/mysql/data/
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:50M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 268435456
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/working/bkps/2014-01-21_01_01_02.log
2014-01-21_01_04_10 xbackup INFO: Last full backup fully prepared (including incrementals): /operation/working/bkps/P_2014-01-20_11_48_01/

Related branches

Alexey Kopytov (community): Approve on 2014-02-25
Alexey Kopytov (community): Approve on 2014-02-25
Scott Haas (sah209) wrote :

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.

Alexey Kopytov (akopytov) wrote :

I agree, the warning is safe to ignore in case of XtraBackup and thus should be removed so it doesn't confuse third-party wrappers.

tags: added: low-hanging-fruit
tags: added: i38702
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers