On Tue, Jan 31, 2012 at 4:01 PM, m.roth@5-cent.us wrote:
On Tue, Jan 31, 2012 at 3:14 PM, Ljubomir Ljubojevic office@plnet.rs wrote:
On 01/31/2012 09:47 PM, Les Mikesell wrote:
No, I'm trying to have rsync make an outbound connection over ssh from the rescue environment and getting what looks like an argument error from ssh. Ssh itself works and I can connect to the same target if I run it directly, and the exact same rsync command lines work from a normal host. Either rsync isn't setting up the remote command right, or ssh isn't allowing it and giving a bad error message.
<snip> > I'm going the other direction (originating the command from the rescue > host), but yes, tar works over ssh, and and ssh works by itself. The > part that doesn't work is ssh when invoked by rsync, either by default > or with an explicit '-essh' argument, and the error message looks like > an ssh argument error so it doesn't even prompt for the password.
AUGH! I think I have it: are the versions of rsync on the rescue instance and the other server the same?
It's not getting that far. I'm getting an error trying to start the local ssh. And at this point I have working VM from the tar copy, _except_ that it isn't matching a driver to the virtual NIC. I'm glad I'm not restoring a real backup with a dead machine here...
Since I don't need this today, I think I'll try ReaR to see if it gets it right. It builds a bootable iso that is supposed to re-install on bare metal.