innobackupex --remote-host is broken

Bug #668128 reported by Baron Schwartz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
New
High
Unassigned

Bug Description

innobackupex --remote-host does not work. Here is shortened output:

[baron@ginger trunk]$ innobackupex-1.5.1 --defaults-file=/home/baron/etc/mysql/server/5.1.41/my.cnf ./ --remote-host=cacti
Version string '' contains invalid data; ignoring: '' at /home/baron/bin/innobackupex-1.5.1 line 1727.
innobackupex-1.5.1: Created backup directory .//2010-10-28_21-04-15
101028 21:04:20 innobackupex-1.5.1: Starting ibbackup with command: xtrabackup_51 --defaults-file="/home/baron/etc/mysql/server/5.1.41/my.cnf" --backup --suspend-at-end --target-dir=.//2010-10-28_21-04-15
innobackupex-1.5.1: Waiting for ibbackup (pid=14688) to suspend
innobackupex-1.5.1: Suspend file '/home/baron/etc/mysql/server/5.1.41/data//xtrabackup_suspended'
>> log scanned up to (268746)
>> log scanned up to (268746)
>> log scanned up to (268746)

And here innobackupex waits forever for xtrabackup, because the path to the xtrabackup_suspended file is wrong. It is really /home/baron/etc/mysql/server/5.1.41/data/2010-10-28_21-04-15/xtrabackup_suspended. If I "touch" that file, then innobackupex continues to work:

101028 21:06:00 innobackupex-1.5.1: Continuing after ibbackup has suspended
innobackupex-1.5.1: Starting to backup InnoDB tables and indexes
innobackupex-1.5.1: to './/2010-10-28_21-04-15'
innobackupex-1.5.1: from original InnoDB data directory '/home/baron/etc/mysql/server/5.1.41/data/'
innobackupex-1.5.1: Backing up file '/home/baron/etc/mysql/server/5.1.41/data//ibdata1'
ibdata1 100% 10MB 10.0MB/s 00:01
101028 21:06:02 innobackupex-1.5.1: Connected to database with mysql child process (pid=14716)
101028 21:06:06 innobackupex-1.5.1: Starting to lock all tables...
>> log scanned up to (268746)
>> log scanned up to (268746)
101028 21:06:16 innobackupex-1.5.1: All tables locked and flushed to disk
101028 21:06:16 innobackupex-1.5.1: Starting to backup .frm, .MRG, .MYD, .MYI,
innobackupex-1.5.1: .TRG, .TRN, .ARM, .ARZ and .opt files in
innobackupex-1.5.1: Backing up file '/home/baron/etc/mysql/server/5.1.41/data//test/t.MYI'
innobackupex-1.5.1: Backing up file '/home/baron/etc/mysql/server/5.1.41/data//test/db.opt'
innobackupex-1.5.1: Backing up file '/home/baron/etc/mysql/server/5.1.41/data//test/t.MYD'
innobackupex-1.5.1: Backing up file '/home/baron/etc/mysql/server/5.1.41/data//test/t.frm'
t.MYI 100% 1024 1.0KB/s 00:00
db.opt 100% 65 0.1KB/s 00:00
t.MYD 100% 63KB 62.7KB/s 00:00
func.frm 100% 8665 8.5KB/s 00:00
time_zone_transition.frm 100% 8686 8.5KB/s 00:00
[... omitted some lines...]
101028 21:06:19 innobackupex-1.5.1: Finished backing up .frm, .MRG, .MYD, .MYI, .TRG, .TRN, .ARM, .ARZ and .opt files
innobackupex-1.5.1: Resuming ibbackup

Here I had to 'kill' and 'rm' and 'touch' a few times, because it got stuck again, and then,

>> log scanned up to (268746)
101028 21:07:10 innobackupex-1.5.1: All tables unlocked
101028 21:07:10 innobackupex-1.5.1: Connection to database server closed
xtrabackup_logfile 100% 0 0.0KB/s 00:00
/home/baron/etc/mysql/server/5.1.41/data//xtrabackup_checkpoints: No such file or directory
innobackupex-1.5.1: Error: Failed to scp file 'cacti:.//2010-10-28_21-04-15/xtrabackup_checkpoints': at /home/baron/bin/innobackupex-1.5.1 line 551.

Finally it ended up with a backup on the remote host, but without the xtrabackup_checkpoints file of course, and it left a bunch of files on the local system.

Changed in percona-xtrabackup:
assignee: nobody → Valentine Gostev (core-longbow)
Revision history for this message
Valentine Gostev (longbow) wrote :

Verified in 1.6

Changed in percona-xtrabackup:
importance: Undecided → High
status: New → Confirmed
Stewart Smith (stewart)
Changed in percona-xtrabackup:
assignee: Valentine Gostev (longbow) → nobody
importance: High → Medium
status: Confirmed → Triaged
Revision history for this message
Stewart Smith (stewart) wrote :
Changed in percona-xtrabackup:
importance: Medium → High
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Could not repeat this when working on bug #787988. Should be verified against the latest version.

Changed in percona-xtrabackup:
status: Triaged → New
Revision history for this message
Stewart Smith (stewart) wrote :

I think this is a duplicate of 787988 which has had a fix committed. If this is is a different bug, please reopen.

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.