# Innobackupex fails but return code is 0

**URL:** <https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825>\
**Category:** Percona XtraBackup\
**Created:** [July 17, 2013, 9:31am UTC](https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825 "2013-07-17T09:31:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dennisjac](https://avatars.discourse-cdn.com/v4/letter/d/c37758/32.png) [@dennisjac](https://forums.percona.com/u/dennisjac)\
**Post date:** [July 17, 2013, 9:31am UTC](https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825/1 "2013-07-17T09:31:03Z")

</div>

Hi,  
I’m trying to write a backup script using innobackupex but I have problems determining that innobackupex ran successfully.  
The log ends with the following output:  
…

> > log scanned up to (9587670370542)  
> > log scanned up to (9587670370542)  
> > log scanned up to (9587670370542)  
> > log scanned up to (9587670370542)  
> > innobackupex: Error: Connection to mysql child process (pid=26032) timedout. (Time limit of 900 seconds exceeded. You may adjust time limit by editing the value of parameter “$mysql\_response\_timeout” in this script.) while waiting for reply to MySQL request: ‘FLUSH TABLES WITH READ LOCK;’ at /usr/bin/innobackupex line 381.  
> > 20130717 01:55:09: Backup finished (duration: 6608 seconds)

I check the return code of the innobackupex command but that is zero even though the command didn’t finish successfully.  
Is this a known bug and what can I do to determine that the script actually ran ok?

---

<div class="post-metadata">

**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\
**Post date:** [July 17, 2013, 3:07pm UTC](https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825/2 "2013-07-17T15:07:14Z")

</div>

Hi,

This error means backup not completed successfully.  
This error explains there is some query which executed bigger than $mysql\_response\_timeout and preventing lock with FTWRL if you taking backup from slave than most probably this is replication event causing this error. You should optimize your queries.  
Other way is to use --no-lock option if all your tables are InnoDB. Also you can use --safe-slave-backup option which stops the replication sql\_thread.

---

<div class="post-metadata">

**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\
**Post date:** [July 17, 2013, 3:27pm UTC](https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825/3 "2013-07-17T15:27:06Z")

</div>

Forgot to mention earlier about innobackupex command reference for further read.  
[www.percona.com/forums/questions-discussions/percona-xtrabackup/10975-innobackupex-fails-but-return-code-is-0](http://www.percona.com/forums/questions-discussions/percona-xtrabackup/10975-innobackupex-fails-but-return-code-is-0)

---

<div class="post-metadata">

**Author:** ![dennisjac](https://avatars.discourse-cdn.com/v4/letter/d/c37758/32.png) [@dennisjac](https://forums.percona.com/u/dennisjac)\
**Post date:** [July 17, 2013, 4:30pm UTC](https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825/4 "2013-07-17T16:30:54Z")

</div>

I understand that this is an error but innobackupex should actually return a proper error code so that backup scripts can detect this. Right now even though the backup failed because of this the innobackupex script results in a return code of zero which means it ran without errors and that’s obviously not correct.

---

<div class="post-metadata">

**Author:** ![Deepakajay](https://avatars.discourse-cdn.com/v4/letter/d/ee59a6/32.png) [@Deepakajay](https://forums.percona.com/u/Deepakajay)\
**Post date:** [September 14, 2015, 11:44pm UTC](https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825/5 "2015-09-14T23:44:32Z")

</div>

Hai,

i have an error while im giving wrong password and username, but i have error code “0” even the backup is not done

innobackupex: got a fatal error with the following stacktrace: at /usr/bin/innobackupex line 3011.  
main::mysql\_connect(“abort\_on\_error”, 1) called at /usr/bin/innobackupex line 1570  
innobackupex: Error: Failed to connect to MySQL server: DBI connect(‘;mysql\_read\_default\_group=xtrabackup’,‘ROO’,…) failed: Access denied for user ‘ROO’@‘localhost’ (using password: YES) at /usr/bin/innobackupex line 2995.

root@mongo1:~# echo $?  
0

---

<div class="post-metadata">

**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\
**Post date:** [September 15, 2015, 1:19am UTC](https://forums.percona.com/t/innobackupex-fails-but-return-code-is-0/2825/6 "2015-09-15T01:19:45Z")

</div>

What version of Percona Xtrabackup you are using ? Can you please also show us the exact command used for backup.  
$ xtrabackup --version
