rsync - Feb 2002 - rsync error: unexplained error (code -1) at main.c(842)

I'm running rsync 2.5.1 on solaris 7 in server mode and getting the
above message when entering the following command:

rsync -vraz --delete hostname::test ./

this is my rsyncd.conf

use chroot = no
max connections = 25
syslog facility = local 3
read only = false

log file = /var/log/rsyncd.log
pid file = /var/log/rsyncd.pid
lock file = /var/log/rsyncd.lock

[test]
path = /export/home/mrl315
comment = rsync test
hosts allow = hostname
secrets file = /etc/rsyncd.secrets

The rsyncd.conf and rsyncd.secrets are owned by root:other and have
read and write permission only for root.

I have setup an rsync server idential to this one on an ultra 10 (this
one is a Sun Enterprise 250) and it works fine.

Regards,

Mike Lefebvre

I've not seen that one before, but I tried to trace it in the source code.
A -1 from main.c line 842 means that start_client() returned a -1 which
means that start_socket_client returned -1 and there are several things
that can cause that.  Mostly they seem to be if the server doesn't do its
part of the protocol properly.  The client error message should definitely
be more descriptive.

Is there anything more descriptive in /var/log/rsyncd.log on the server?
The real problem is probably on the server.

- Dave Dykstra

On Tue, Feb 05, 2002 at 09:52:52AM -0500, MICHAEL R. LEFEBVRE
wrote:
> I'm running rsync 2.5.1 on solaris 7 in server mode and getting the
> above message when entering the following command:
> 
> rsync -vraz --delete hostname::test ./
> 
> this is my rsyncd.conf
> 
> use chroot = no
> max connections = 25
> syslog facility = local 3
> read only = false
> 
> log file = /var/log/rsyncd.log
> pid file = /var/log/rsyncd.pid
> lock file = /var/log/rsyncd.lock
> 
> [test]
> path = /export/home/mrl315
> comment = rsync test
> hosts allow = hostname
> secrets file = /etc/rsyncd.secrets
> 
> The rsyncd.conf and rsyncd.secrets are owned by root:other and have
> read and write permission only for root.
> 
> I have setup an rsync server idential to this one on an ultra 10 (this
> one is a Sun Enterprise 250) and it works fine.
> 
> Regards,
> 
> Mike Lefebvre