Rsync Error..

Jim Salter jim at
Fri Apr 23 23:37:55 GMT 2004

Tim already answered your question for you.  Your remote system is not 
answering on port 514, only on port 513.  See your OS's rsh man page for 
further details - this isn't really an rsync question, it's an rsh question.

> However when I first give "rsh" and after remote login when i give "which rsync" ;  i get the following output 
> /usr/local/bin/rsync.
> Jim Salter <jim at> wrote:
> Clearly, if you can't execute the "which" command remotely, rsh is _not_ 
> working "perfectly fine." If you can't use it for remote command 
> execution, it isn't going to serve as an rsync transport.
> Jim Salter
> JRS Systems
>>when i gave "rsh which rsync" at the source system i got the following error
>> Connection refused
>>"rsh" works perfectly fine.
>>What could be the problem..?
>>Tim Conway wrote:
>>rsh which rsync
>>I expect you'll get something like "no rsync in /usr/bin /usr/ccs/bin 
>>/usr/bin/X11 /usr/contrib/bin /usr/local/bin ." Some systems don't report 
>>the remote shell connection open until the called remote program comes up, 
>>so one missing from the path can look like a network timeout. I don't 
>>remember if that's true of any FreeBSD.
>>If this is the case, use --rsync-path=/wherever/it/is/on/
>>Tim Conway
>>Unix System Administration
>>Contractor - IBM Global Services
>>conway at
>>opening connection using rsh rsync --server -vvbnlogDtprz . 
>> operation timed out
>>rsync: connection unexpectedly closed (0 bytes read so far)
>>rsync error: error in rsync protocol data stream (code 12) at io.c(189)
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Photos: High-quality 4x6 digital prints for 25?

More information about the rsync mailing list