If I boot a 5.7 install disk with 'linux rescue selinux=0', let it start the network and detect the installed system, ssh seems to work, but rsync fails with "rsync: connection unexpectedly closed (0 bytes received so far) [receiver]). Shouldn't it work as long as the underlying ssh connection works? It doesn't prompt for the ssh password and using -essh doesn't change it.
Les Mikesell writes:
If I boot a 5.7 install disk with 'linux rescue selinux=0', let it start the network and detect the installed system, ssh seems to work, but rsync fails with "rsync: connection unexpectedly closed (0 bytes received so far) [receiver]). Shouldn't it work as long as the underlying ssh connection works? It doesn't prompt for the ssh password and using -essh doesn't change it.
Les,
What commands are you using exactly? To or from the rescued host? Also, are you using ssh non-standard ports?
-- Nux! www.nux.ro
On Tue, Jan 31, 2012 at 12:29 PM, nux@li.nux.ro wrote:
Les Mikesell writes:
If I boot a 5.7 install disk with 'linux rescue selinux=0', let it start the network and detect the installed system, ssh seems to work, but rsync fails with "rsync: connection unexpectedly closed (0 bytes received so far) [receiver]). Shouldn't it work as long as the underlying ssh connection works? It doesn't prompt for the ssh password and using -essh doesn't change it.
What commands are you using exactly? To or from the rescued host? Also, are you using ssh non-standard ports?
It is from the rescued host - basically a: rsync -essh otherhost:/path .
ssh otherhost 'cd /path && tar -cf - ' | tar -xvf - seems to be working, so it is not related to network connectivity or ssh.
-- Les Mikesell lesmikesell@gmail.com
Les Mikesell writes:
On Tue, Jan 31, 2012 at 12:29 PM, nux@li.nux.ro wrote:
Les Mikesell writes:
If I boot a 5.7 install disk with 'linux rescue selinux=0', let it start the network and detect the installed system, ssh seems to work, but rsync fails with "rsync: connection unexpectedly closed (0 bytes received so far) [receiver]). Shouldn't it work as long as the underlying ssh connection works? It doesn't prompt for the ssh password and using -essh doesn't change it.
What commands are you using exactly? To or from the rescued host? Also, are you using ssh non-standard ports?
It is from the rescued host - basically a: rsync -essh otherhost:/path .
ssh otherhost 'cd /path && tar -cf - ' | tar -xvf - seems to be working, so it is not related to network connectivity or ssh.
That's odd, try rsync -e 'ssh -v' to get some more details. Also you will want to use some parameters to rsync (like -av or maybe even -z for compression etc).
-- Nux! www.nux.ro
On Tue, Jan 31, 2012 at 1:07 PM, nux@li.nux.ro wrote:
What commands are you using exactly? To or from the rescued host? Also, are you using ssh non-standard ports?
It is from the rescued host - basically a: rsync -essh otherhost:/path .
ssh otherhost 'cd /path && tar -cf - ' | tar -xvf - seems to be working, so it is not related to network connectivity or ssh.
That's odd, try rsync -e 'ssh -v' to get some more details. Also you will want to use some parameters to rsync (like -av or maybe even -z for compression etc).
I'm getting a usage: ssh [bunch of ssh options] like it is giving the wrong command line to ssh. Or maybe the lack of an /etc/ssh/ssh_config in this environment is breaking it, although my own ssh commands and connections seem to work. I haven't done the chroot into the installed mount since I was planning to overwrite it.
-
Les Mikesell -
nux＠li.nux.ro