1.6.4-313 loses master log info

Bug #907147 reported by Ren Xiaolei on 2011-12-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov

Bug Description


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

Related branches

Alexey Kopytov (akopytov) wrote :

Confirmed, it's a regression introduced in 1.6.4.

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"

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  Edit
Everyone can see this information.

Other bug subscribers