RSYNC problem - error in IPC code

Sun Jan 28 23:00:00 GMT 2007

I don't think it's about paco (remote) at all. I can rsync paco with 
itself no problem:
=================================================
root@paco:~/test# rsync -ar test localhost:~/test2
=================================================
When I try to rsync local with remote or local with local, ssh or no ssh 
the same problem occurs.
=================================================
admin@n:~/rsync# rsync test test2
rsync: pipe: Connection refused (111)
rsync error: error in IPC code (code 14) at 
/home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(117)
admin@n:~/rsync# rsync -a test root@paco:~/test
rsync: pipe: Connection refused (111)
rsync error: error in IPC code (code 14) at 
/home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(55)
admin@n:~/rsync# rsync -e ssh -a test root@paco:~/test
rsync: pipe: Connection refused (111)
rsync error: error in IPC code (code 14) at 
/home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(55)
=================================================
Any other ideas?
Thanks,
Andrey.
Jean-Claude Gervais wrote:
> Then I think it means your ssh transport is fine but your rsync service
> daemon is not started on paco.
>> On Sun, 2007年01月28日 at 14:00 -0800, it wrote:
>>> Thanks, I just tried specifying explicitly SSH, and still the same
>> error:
>> ====================================================
>> admin@n:~/rsync# rsync -e ssh test test2
>> rsync: pipe: Connection refused (111)
>> rsync error: error in IPC code (code 14)
>> at /home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(117)
>> admin@n:~/rsync# rsync -e ssh test root@paco:~/test
>> rsync: pipe: Connection refused (111)
>> rsync error: error in IPC code (code 14)
>> at /home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(55)
>> admin@n:~/rsync# RSYNC_RSH=ssh
>> admin@n:~/rsync# rsync -a test test2
>> rsync: pipe: Connection refused (111)
>> rsync error: error in IPC code (code 14)
>> at /home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(117)
>> ====================================================
>>>> Andrey.
>>>> Jean-Claude Gervais wrote: 
>>>>> rsync normally uses port 873
>>>>>> http://rsync.samba.org/ftp/rsync/rsync.html
>>>>>> The link has info about using rsync over ssh, do a find for ssh on the
>>> page
>>>>>>>>> On Sun, 2007年01月28日 at 11:45 -0800, it wrote:
>>>>>>>>>> Hi Jean-Claude,
>>>>>>>> I'm not quite understanding the connection between rsync and telnet.
>>>> I'm not planning to use telnet, I want to use rsync over ssh.
>>>> Rsync is not even working for local transfers - same error.
>>>>>>>> Here's the output from the command prompt:
>>>> ======================================================
>>>> C:\Documents and Settings\admin>telnet paco 22
>>>> Connecting To paco...Could not open connection to the host, on port
>>>> 22: Connect
>>>> failed
>>>>>>>> C:\Documents and Settings\admin>telnet localhost 22
>>>> Connecting To localhost...Could not open connection to the host, on
>>>> port 22: Con
>>>> nect failed
>>>> ======================================================
>>>>>>>> I can SSH into both of these no problem:
>>>> ======================================================
>>>> admin@n:~/rsync# ssh root@paco
>>>> Last login: Sun Jan 28 11:16:36 2007 from
>>>> h-67-101-97-239.snfccasy.dynamic.covad.net
>>>> Linux paco 2.4.24 #1 Tue Feb 3 18:30:22 PST 2004 i686 GNU/Linux
>>>> No mail.
>>>> root@paco:~# exit
>>>> logout
>>>> Connection to paco closed.
>>>> admin@n:~/rsync# ssh localhost
>>>> admin@localhost's password:
>>>> Last login: Fri Jan 26 14:59:11 2007 from localhost
>>>> Fanfare!!!
>>>> You are successfully logged in to this server!!!
>>>> admin@n:~#
>>>> ======================================================
>>>>>>>> Rsync is not working regardless of connection, it gives the same error
>>>> even if I specify the names of folders on localhost that don't exist.
>>>> ======================================================
>>>> admin@n:~/rsync# l
>>>> total 3
>>>> drwxrwxrwx+ 2 admin None 0 Jan 26 13:52 test
>>>> drwxrwxrwx+ 2 admin None 0 Jan 26 14:09 test2
>>>> admin@n:~/rsync# rsync test test2
>>>> rsync: pipe: Connection refused (111)
>>>> rsync error: error in IPC code (code 14)
>>>> at /home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(117)
>>>> admin@n:~/rsync# rsync lala lala
>>>> rsync: pipe: Connection refused (111)
>>>> rsync error: error in IPC code (code 14)
>>>> at /home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(117)
>>>> ======================================================
>>>>>>>> And, as I said, I don't even have /home/lapo directory on my computer.
>>>>>>>> Thanks,
>>>> Andrey.
>>>>>>>>>>>> Jean-Claude Gervais wrote: 
>>>>>>>>>>>>> I meant you open a DOS prompt on the windows machine and type
>>>>> telnet linuxmachinename 22
>>>>>>>>>> With that you'll see if the TCP connection can be established or not.
>>>>>>>>>> On Sun, 2007年01月28日 at 11:21 -0800, it wrote:
>>>>>>>>>>>>>>>>>>>>> Telnet?
>>>>>>>>>>>> I can SSH into localhost or the remote hosts no problem.
>>>>>>>>>>>> The remote host (Linux) rsync works fine:
>>>>>> drwxr-xr-x 2 root root 4096 Jan 28 11:16 test
>>>>>> drwxr-xr-x 2 root root 4096 Jan 28 11:16 test2
>>>>>> root@paco:~/test# rsync -ar test test2
>>>>>>>>>>>> The windows/cygwin box is the one that is giving error. I don't think
>>>>>> it's another host's configuration that's the problem.
>>>>>>>>>>>> admin@n:~/rsync# rsync test test2
>>>>>> rsync: pipe: Connection refused (111)
>>>>>> rsync error: error in IPC code (code 14)
>>>>>> at /home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(117)
>>>>>>>>>>>> local -> local should copy just fine, anyway.
>>>>>>>>>>>> I don't even have /home/lapo directory. Any ideas what it's talking
>>>>>> about?
>>>>>>>>>>>> Thanks,
>>>>>> Andrey.
>>>>>>>>>>>> Jean-Claude Gervais wrote: 
>>>>>>>>>>>>>>>>>>>>>>>>> I think the IPC (inter-process-comm) error is being reported because of
>>>>>>> the first reported error; connection refused.
>>>>>>> It means that you are reaching the host, but there is no process bound
>>>>>>> to that port. 
>>>>>>>>>>>>>> I suggest you telnet to the host.
>>>>>>> Ex
>>>>>>> 	telnet test 22
>>>>>>>>>>>>>> If it connects but then proceeds no further there IS a process listening
>>>>>>> on the port.
>>>>>>> else if telnet immediately reports a connection error then there is NO
>>>>>>> process on the host listening at port 22.
>>>>>>>>>>>>>> If the daemon process IS started but is unreachable, it is not
>>>>>>> authorized to listen for connections on port 22 on the interface your
>>>>>>> connection is coming in on. (localhost-only)
>>>>>>>>>>>>>> If the daemon is NOT started on the host, check the host's config.
>>>>>>>>>>>>>> This one is trickier because service invocation methods can be quite
>>>>>>> different between linux distributions.
>>>>>>>>>>>>>> J
>>>>>>>>>>>>>> On Sun, 2007年01月28日 at 09:35 -0800, it wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Greetings,
>>>>>>>>>>>>>>>> I'm having a problem with rsync. I want to sync my Windows box to a 
>>>>>>>> Linux server using rsync and I get the following error when I try to do 
>>>>>>>> any command. Remote or local.
>>>>>>>>>>>>>>>> admin@n:~/rsync# rsync -a test test2
>>>>>>>> rsync: pipe: Connection refused (111)
>>>>>>>> rsync error: error in IPC code (code 14) at 
>>>>>>>> /home/lapo/packaging/tmp/rsync-2.6.6/pipe.c(117)
>>>>>>>> (test and test2 are local folders in ~/rsync directory, remote gives the 
>>>>>>>> same error)
>>>>>>>>>>>>>>>> Any ideas?
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>> Andrey.
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>>>>>>>> Problem reports: http://cygwin.com/problems.html
>>>>>>>> Documentation: http://cygwin.com/docs.html
>>>>>>>> FAQ: http://cygwin.com/faq/
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/