rsync - Oct 2005 - Help with sincronizing two directories on remote servers

Dear friends,

a newbie here.

we have two webservers, a and b, both of them with rsync 
installed.

We would like to rsync one directory on one server with 
another directpory on another server.

What I do is to go to one of the server (server a) as root 
using ssh, navigate to the directory, and write

rsync -avz username@serverb:directory/     ./

But it does not work.

Am I doing something wrong?

Thanks in advance
-- 
symbulos - ethical services for your organisation
website www.symbulos.com

I apologise for the incongruous posting.

We have two webservers, a and b, both of them with rsync 
installed.

We would like to rsync one directory on one server with 
another directory on another server.

What I do is to go to one of the server (server a) as root 
using ssh, navigate to the directory, and write

rsync -avz username@serverb:directory/     ./

This is the error we get

ssh: connect to host 80.81.131.173 port 22: Connection 
refused
rsync: connection unexpectedly closed (0 bytes received so 
far) [receiver]
rsync error: error in rsync protocol data stream (code 12) 
at io.c(359)

Thanks in advance

Corrado

Corrado, Rina, John, Judith
-- 
symbulos - ethical services for your organisation
website www.symbulos.com

On Mon 10 Oct 2005, symbulos - ethical services (external mailing lists)
wrote:
> 
> What I do is to go to one of the server (server a) as root 
> using ssh, navigate to the directory, and write
> 
> rsync -avz username@serverb:directory/     ./
> 
> This is the error we get
> 
> ssh: connect to host 80.81.131.173 port 22: Connection 
> refused
This simply means that ssh is not running as a daemon on the remote
system (serverb). Ensure that you can login as "username" via ssh on
that system before trying rsync over ssh.


Paul Slootman

The fact is, we can login as username on this server. 
Instead of giving an error should then ask me for password, 
I think.

Corrado 

On Monday 10 Oct 2005 17:44, Paul Slootman wrote:
> On Mon 10 Oct 2005, symbulos - ethical services (external 
mailing lists) wrote:
> > What I do is to go to one of the server (server a) as
> > root using ssh, navigate to the directory, and write
> >
> > rsync -avz username@serverb:directory/     ./
> >
> > This is the error we get
> >
> > ssh: connect to host 80.81.131.173 port 22: Connection
> > refused
>
> This simply means that ssh is not running as a daemon on
> the remote system (serverb). Ensure that you can login as
> "username" via ssh on that system before trying rsync
> over ssh.
>
>
> Paul Slootman
-- 
symbulos - ethical services for your organisation
website www.symbulos.com

Strangely we can login as ssh from the pc here, but we 
cannot login as ssh from the other remote server (ssh: 
connect to host serverb port 22: Connection refused).

What is happening? I do not understand.

Corrado 

On Monday 10 Oct 2005 17:44, Paul Slootman wrote:
> On Mon 10 Oct 2005, symbulos - ethical services (external 
mailing lists) wrote:
> > What I do is to go to one of the server (server a) as
> > root using ssh, navigate to the directory, and write
> >
> > rsync -avz username@serverb:directory/     ./
> >
> > This is the error we get
> >
> > ssh: connect to host 80.81.131.173 port 22: Connection
> > refused
>
> This simply means that ssh is not running as a daemon on
> the remote system (serverb). Ensure that you can login as
> "username" via ssh on that system before trying rsync
> over ssh.
>
>
> Paul Slootman
-- 
symbulos - ethical services for your organisation
website www.symbulos.com

symbulos - ethical services (external mailing lists)
wrote:
> I apologise for the incongruous posting.
> 
> We have two webservers, a and b, both of them with rsync 
> installed.
> 
> We would like to rsync one directory on one server with 
> another directory on another server.
> 
> What I do is to go to one of the server (server a) as root 
> using ssh, navigate to the directory, and write
> 
> rsync -avz username@serverb:directory/     ./
> 
> This is the error we get
> 
> ssh: connect to host 80.81.131.173 port 22: Connection 
> refused
this is the important part and it means that port 22 does not accept 
connections at all.
Make sure that
a) sshd is running at 80.81.131.173
b) any firewall in between does not block connections from you
c) sshd is licening at port 22
> rsync: connection unexpectedly closed (0 bytes received so 
> far) [receiver]
> rsync error: error in rsync protocol data stream (code 12) 
> at io.c(359)
> 
> Thanks in advance
> 
> Corrado
> 
> Corrado, Rina, John, Judith

On Monday 10 Oct 2005 17:32, symbulos - ethical services (external mailing 
lists) wrote:
> I apologise for the incongruous posting.
>
> We have two webservers, a and b, both of them with rsync
> installed.
>
> We would like to rsync one directory on one server with
> another directory on another server.
>
> What I do is to go to one of the server (server a) as root
> using ssh, navigate to the directory, and write
>
> rsync -avz username@serverb:directory/     ./
>
> This is the error we get
>
> ssh: connect to host 80.81.131.173 port 22: Connection
> refused
# tcpcheck 10 80.81.131.173:22
80.81.131.173:22 failed:  timed out

you have no ssh running there.
> rsync: connection unexpectedly closed (0 bytes received so
> far) [receiver]
> rsync error: error in rsync protocol data stream (code 12)
> at io.c(359)
>
> Thanks in advance
>
> Corrado
>
> Corrado, Rina, John, Judith
> --
> symbulos - ethical services for your organisation
> website www.symbulos.com
-- 
-----------------
Bob Hutchinson
Midwales dot com
-----------------

Can you simply run -netstat- on your PCs and check if you can see something
listening on port 22 ?

It may also be helpful if you can be more specific about what platforms you
experience that problem.


Maybe your ssh daemon is being activated via tcp-wrappers and there is something
blocking between ?

Rgrds Tev
> -----Original Message-----
> From: rsync-bounces+tevfik=itefix.no@lists.samba.org 
> [mailto:rsync-bounces+tevfik=itefix.no@lists.samba.org] On 
> Behalf Of symbulos - ethical services (external mailing lists)
> Sent: 10. oktober 2005 19:03
> To: rsync@lists.samba.org
> Subject: Update: Re: Help with synchronizing two directories 
> on remoteservers
> 
> Strangely we can login as ssh from the pc here, but we cannot 
> login as ssh from the other remote server (ssh: 
> connect to host serverb port 22: Connection refused).
> 
> What is happening? I do not understand.
> 
> Corrado 
> 
> On Monday 10 Oct 2005 17:44, Paul Slootman wrote:
> > On Mon 10 Oct 2005, symbulos - ethical services (external
> mailing lists) wrote:
> > > What I do is to go to one of the server (server a) as root using 
> > > ssh, navigate to the directory, and write
> > >
> > > rsync -avz username@serverb:directory/     ./
> > >
> > > This is the error we get
> > >
> > > ssh: connect to host 80.81.131.173 port 22: Connection refused
> >
> > This simply means that ssh is not running as a daemon on the remote 
> > system (serverb). Ensure that you can login as "username" 
> via ssh on 
> > that system before trying rsync over ssh.
> >
> >
> > Paul Slootman
> 
> --
> symbulos - ethical services for your organisation website 
> www.symbulos.com
> 
> --
> To unsubscribe or change options: 
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: 
> http://www.catb.org/~esr/faqs/smart-questions.html
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3022 bytes
Desc: not available
Url :
http://lists.samba.org/archive/rsync/attachments/20051012/6666b3e9/smime.bin

Here are answers to all you questions, I hope.

The platforms are:

1)administration desktop (pc here)
Mandriva LE2005

2)servera
Debian 3.0

3)serverb
Fedora Core 3

ssh from servera to serverb (in a remote ssh shell from "pc 
here") is working

ssh from serverb to severa (in a remote ssh shell from "pc 
here") is not working with the error 
(ssh: connect to host serverb port 22: Connection refused).

The problem is we need to move files from serverb to server 
a.