innobackupex doesn't pass port option to both ssh and scp

Reported by Baron Schwartz on 2011-03-12
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Low
Sergei Glushchenko
1.6
Low
Sergei Glushchenko
2.0
Low
Sergei Glushchenko

Bug Description

A user reported that when using --remote-host to a non-standard SSH port, the tool doesn't pass the correct port to both ssh and scp, which use different options for port number (-p vs -P). A patch is attached at http://forum.percona.com/index.php/m/6756/

Stewart Smith (stewart) wrote :

patch is probably okay, but we should get actual diff from Patrick so we can apply it.

Changed in percona-xtrabackup:
status: New → Confirmed
Stewart Smith (stewart) wrote :

Hey Patrick, can you possibly either a) put up a branch with fix in it or b) add a patch to this bug report?

Stewart Smith (stewart) on 2011-05-19
tags: added: low-hanging-fruit
Stewart Smith (stewart) on 2011-05-20
Changed in percona-xtrabackup:
importance: Undecided → Low
status: Confirmed → Triaged

got our SSH Servers running on non-Standard Port - without the ability to specify the port we can't use remote backup functionality.
Any fix in seight?

Alexey Kopytov (akopytov) wrote :

Andreas,

It's not currently targeted to any specific milestones. But we use bug heat to prioritize bugs for upcoming releases. So clicking on the "Does this bug affect you?" link will raise the heat value for this bug, and thus make it more likely to be scheduled for the next release.

It was decided to add --sshopt option in addition to --scpopt. It will allow to provide custom parameters to both ssh and scp tools.

Valentine Gostev (longbow) wrote :

Both scp and ssh understand "-F /path/to/ssh/config" option.

I believe it is just enough to pass -F option to ssh/scp and force user to keep config of ssh connection in file.

Passing options for ssh and scp separately is more flexible. At the moment there is no way to pass custom options to ssh.

I beleive that one could use ~/.ssh/config as a workaround.

Andrew Noonan (anoonan) wrote :

This also affects being able to use arbitrary SSH keys for remote backups. We have a specific key used to login to the backup server from the database server. The backup process runs as root, so while we are able to specify a key using the scpopts, the ssh part of the backup fails unless root's private key is the backup key, which we don't want to do, or share the same ssh config, which we again don't really want to do. Having a --sshopt option seems much better for us, as we cannot do remote backups without hacking up the script until this is completed.

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

Other bug subscribers