questions about "connection refused"

[jw schultz]

On Tue, Aug 12, 2003 at 03:52:02PM +0800, tongw wrote:
> Dear all:
>         I installed the rsync 2.5.4 in my two machines (192.168.1.30 and
> 192.168.1.120, both are AIX OS) to backup data each other. The
> software`s installation is ok, and I can copy local files. But when I
> try to backup data between two machines, there reports some errors: 
> 
> >./bin/rsync -avz tong at 192.168.1.30::web ./backup-3000/
> rsync: failed to connect to 192.168.1.30: Connection refused
> rsync error: error in socket IO (code 10) at clientserver.c(89)

No rsync daemon running.

> another try: 
> >./bin/rsync -avz tong at 192.168.1.30:/BGI/UCSC-mirror/bin/rsync-2.5.4/man
> ./backup-3000/
> rshd: 0826-813 Permission is denied.
> rsync: connection unexpectedly closed (0 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(151)

That is an rsh problem.  You'd be more secure using ssh
instead of rsh anyway.

You probably should decide whether you want to run an rsync
daemon or connect via a remote shell utility.  Usually the
easiest to get working is via a remote shell utility,
preferably ssh.  There are pros and cons to each.

>     In fact, I have set up the rsyncd.conf file in the 192.168.1.30 as
> the following, I don`t know how to deal with the errors. 
> 
> uid = nobody
> gid = nobody 
> use chroot = no
> max connections = 4 
> pid file = /var/run/rsyncd.pid 
> lock file = /var/run/rsync.lock 
> log file = /var/log/rsyncd.log 
> 
> [web] # just a test
> path = /BGI/UCSC-mirror/bin/apache_1.3.27
> comment = tmp backup directory
> ignore errors
> read only = yes 
> list = no 
> auth users = tong 
> secrets file = /etc/backserver.pas
> hosts allow = 192.168.1.120
> 
>     Another question, when I initiate the rsync server in 192.168.1.30
> by "rsync --daemon" command, the script is soon completed, no errors or
> runing information. How can I know whether the "daemon" mode of rsync
> has been initiated?

It isn't a script and the described behaviour is correct.
Using --daemon it should disassociate from the controlling
tty and process group.  You know it was successful by
looking for it with ps, reading the log file, or connecting
to it.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt