slave-info parse error on 2.4.8

Bug #1711010 reported by Jervin R
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Status tracked in 2.4
2.3
Invalid
Undecided
Unassigned
2.4
Fix Released
High
Vasily Nemkov

Bug Description

On 2.4.8, when using --slave-info and backing up 5.7 instances, the master binary log coordinates is not properly displayed in the logs. 2.4.7 seems to work fine.

5.6.36, pxb 2.3.9:

170815 17:37:50 Backup created in directory '/p/bkp/stor/full/2017_08_15-17_37_48/'
MySQL binlog position: filename 'mysql-bin.000001', position '540387250'
MySQL slave binlog position: master host '127.0.0.1', filename 'mysql-bin.000001', position '540387250'

[vagrant@pxb ~]$ cat /p/bkp/stor/full/2017_08_15-17_36_18/xtrabackup_slave_info
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=540387250;

5.6.36, pxb 2.4.8

170815 17:42:54 Backup created in directory '/p/bkp/stor/full/2017_08_15-17_42_52/'
MySQL binlog position: filename 'mysql-bin.000001', position '540387250'
MySQL slave binlog position:
m
170815 17:42:54 [00] Writing /p/bkp/stor/full/2017_08_15-17_42_52/backup-my.cnf

[vagrant@pxb ~]$ cat /p/bkp/stor/full/2017_08_15-17_42_52/xtrabackup_slave_info
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=540387250;

5.7.18, pxb 2.4.8

170815 17:48:40 Backup created in directory '/p/bkp/stor/full/2017_08_15-17_48_39/'
MySQL binlog position: filename 'mysql-bin.000001', position '648600638'
MySQL slave binlog position:
m
170815 17:48:40 [00] Writing /p/bkp/stor/full/2017_08_15-17_48_39/backup-my.cnf

[vagrant@pxb ~]$ cat /p/bkp/stor/full/2017_08_15-17_48_39/xtrabackup_slave_info
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=649652486;
[vagrant@pxb ~]$

Revision history for this message
Vasily Nemkov (vasily.nemkov) wrote :
Revision history for this message
Vasily Nemkov (vasily.nemkov) wrote :

Will update the test case in order to verify the fix.

Revision history for this message
Vasily Nemkov (vasily.nemkov) wrote :
Revision history for this message
Vasily Nemkov (vasily.nemkov) wrote :

Updated the test case in a PR above, the issue itself was fixed in https://bugs.launchpad.net/percona-xtrabackup/2.3/+bug/1707918

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

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.