1.6.4-313 loses master log info

Bug #907147 reported by Ren Xiaolei
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Undecided
Alexey Kopytov
1.6
Fix Released
Undecided
Alexey Kopytov
2.0
Fix Released
Undecided
Alexey Kopytov

Bug Description

xtrabackup-1.6.4-313.rhel5

Execute innobackupex script on a master MySQL server, got a line below:
"innobackupex: MySQL binlog position: filename 'xtrabackup', position ping 5"

similar line in backupdir/xtrabackup_binlog_info file:
"xtrabackup ping 5"

OLD version xtrabackup-1.6.3-292.rhel5 works fine. It might be a new bug introduced in 1.6.4-313

Tags: binlog

Related branches

Revision history for this message
Alexey Kopytov (akopytov) wrote :

Confirmed, it's a regression introduced in 1.6.4.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

The fix is:

=== modified file 'innobackupex'
--- innobackupex 2011-12-17 03:21:32 +0000
+++ innobackupex 2011-12-21 05:30:23 +0000
@@ -1165,7 +1165,7 @@ sub write_binlog_info {
     # get "show master status" output lines (2) from mysql output
     file_to_array($mysql_stdout, \@lines);
     foreach my $line (@lines) {
- if ($line =~ m/innobackup hello/) {
+ if ($line =~ m/xtrabackup ping/) {
             # this is a hello message, ignore it
         } else {
             # this is output line from "show master status"

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

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.