innobackupex returns exit code 0 when it fails

Bug #1406091 reported by Miguel Angel Nieto
8
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

A user with 2.0.8 reported that when innobackupex fails with the following errors:

xtrabackup: error: expected log block no. 684572520, but got no. 698728224 from the log file.
xtrabackup: error: it looks like InnoDB log has wrapped around before xtrabackup could process all records due to either log copying being too slow, or log files being too small.
xtrabackup: Error: xtrabackup_copy_logfile() failed.

or

141228 0:49:20 InnoDB: Operating system error number 24 in a file operation.
InnoDB: Error number 24 means 'Too many open files'.

It returns exit code 0. I remember that a similar bug was reported while ago, but I cannot find if so I don't know if it is fixed or not.

Tags: i49443
tags: added: i49443
Revision history for this message
Nilnandan Joshi (nilnandan-joshi) wrote :
Download full text (6.1 KiB)

Unable to reproduce the same with xtrabackup 2.0.8 on both the scenarios.

root@desktop:/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin# ./innobackupex --user=root --password=root --ibbackup=/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin/xtrabackup_56 /home/nilnandan/backup/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

...
innobackupex: Using mysql Ver 14.14 Distrib 5.6.21-70.1, for debian-linux-gnu (x86_64) using EditLine wrapper
Warning: Using a password on the command line interface can be insecure.
innobackupex: Using mysql server version Copyright (c) 2009-2014 Percona LLC and/or its affiliates

innobackupex: Created backup directory /home/nilnandan/backup/2015-01-06_12-31-21
150106 12:31:21 innobackupex: Starting mysql with options: --password=xxxxxxxx --user='root' --unbuffered --
150106 12:31:21 innobackupex: Connected to database with mysql child process (pid=13166)
150106 12:31:23 innobackupex: Connection to database server closed

150106 12:31:23 innobackupex: Starting ibbackup with command: /home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin/xtrabackup_56 --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/home/nilnandan/backup/2015-01-06_12-31-21 --tmpdir=/tmp
innobackupex: Waiting for ibbackup (pid=13173) to suspend
innobackupex: Suspend file '/home/nilnandan/backup/2015-01-06_12-31-21/xtrabackup_suspended'

/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin/xtrabackup_56 version 2.0.8 for MySQL server 5.6.10 Linux (x86_64) (revision id: 587)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 1048576
>> log scanned up to (1873735705)
InnoDB: Allocated tablespace 3, old maximum was 0
[01] Copying ./ibdata1 to /home/nilnandan/backup/2015-01-06_12-31-21/ibdata1
>> log scanned up to (1875519844)
>> log scanned up to (1876433279)
...
>> log scanned up to (1896730431)
xtrabackup: error: log block numbers mismatch:
xtrabackup: error: expected log block no. 3704552, but got no. 3708640 from the log file.
xtrabackup: error: it looks like InnoDB log has wrapped around before xtrabackup could process all records due to either log copying being too slow, or log files being too small.
xtrabackup: Error: xtrabackup_copy_logfile() failed.
innobackupex: Error: ibbackup child process has died at ./innobackupex line 386.
root@desktop:/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin#
root@desktop:/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin# echo $?
2
root@desktop:/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin#

With 'Too many open files' error,

root@desktop:/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin# ./innobackupex --user=root --password=root --ibbackup=/home/nilnandan/Downloads/percona-xtrabackup-2.0.8/bin/xtrabackup_56 /home/nilnandan/backup/

...

innobackupex: Usi...

Read more...

Changed in percona-xtrabackup:
status: New → Incomplete
no longer affects: percona-xtrabackup/2.2
no longer affects: percona-xtrabackup/2.1
no longer affects: percona-xtrabackup/2.0
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-1311

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.