Traceback in innobackupex

Bug #1182841 reported by Raghavendra D Prabhu on 2013-05-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released
Alexey Kopytov
Won't Fix
Fix Released
Alexey Kopytov

Bug Description

In crashes like it would be nice if there is a traceback (much like backtrace we see in C).

From I have found that adding the following helps:

--- /usr/bin/innobackupex 2013-05-18 01:05:42.000000000 +0530
+++ /home/raghu/innobackupex 2013-05-22 16:07:49.492476124 +0530
@@ -36,6 +36,9 @@


+use Carp;
+$SIG{ __DIE__ } = sub { Carp::confess( @_ ) };
 # required Perl version (5.005)
 my @required_perl_version = (5, 0, 5);
 my $required_perl_version_old_style = 5.005;

It produces backtrace like:

 at /usr/bin/innobackupex line 40
        main::__ANON__('innobackupex: Error: \x{a}Error executing \'FLUSH TABLES WITH REA...') called at /usr/bin/innobackupex line 392
        main::Die('\x{a}Error executing \'FLUSH TABLES WITH READ LOCK\': DBD::mysql:...') called at /usr/bin/innobackupex line 1451
        main::mysql_query('HASH(0x106fe00)', 'FLUSH TABLES WITH READ LOCK') called at /usr/bin/innobackupex line 1623
        main::mysql_lockall('HASH(0x106fe00)') called at /usr/bin/innobackupex line 436
        main::backup() called at /usr/bin/innobackupex line 312

Full log here:

(Note: The crash in the log is induced by me to produce backtrace
and is not a PXB bug)

Related branches

tags: added: low-hanging-fruit
Philip Stoev (philip-stoev-f) wrote :

Galera is affected a bit by this change -- a false positive stack trace is printed in the error log during SST:

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers