Bug 1633 - error in rsync protocol data stream (code 12) at io.c(359)
Summary: error in rsync protocol data stream (code 12) at io.c(359)
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 2.6.3
Hardware: Alpha OSF/1
: P3 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL: http://www.snailbook.com/faq/scp-ossh...
Depends on:
Reported: 2004-08-19 16:43 UTC by Russ Ramsey
Modified: 2005-04-01 11:22 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Russ Ramsey 2004-08-19 16:43:33 UTC
Using rsync from OSF with commercial ssh.com to Solaris with Sun ssh works fine.
Using rsync from Solaris with Sun (OpenSSH derived) to OSF fails with:
select: Bad file number
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(359)

This sounds like the scp compatibility problem between the two.  Does rsync use 
ssh protocol 2 or protocol 1 which scp uses?  Because protocol 1 is not running 
on the OSF machine.
Comment 1 Wayne Davison 2004-09-18 10:11:20 UTC
Rsync doesn't use any ssh protocol itself -- it just calls ssh and lets it do
whatever you've configured ssh to do.  You can affect this by either setting
per-host config items in your ssh config file, or by setting ssh options using
the --rsh (-e) option, like this:

   --rsh="ssh -2"

You can also specify 2 -v options to see what command rsync is running to talk
to the remote host and you can try running that outside of rsync to see what it
does (you can substitite a different remote command than rsync too, such as