Hi,
I'm sure I'm missing something simple but I can't find it.
We just set up a new server with Fedora Core 2 and I'm trying to set up
an rsync to it. I've had this working to a Debian machine, so I'm
almost sure my config is rsync config is good.
I'm running rsync 2.6.2-1 in daemon mode on the server with the
following config file:
log file = /var/log/rsyncd.log
hosts allow = 172.16.0.0/255.255.0.0
secrets file = /etc/rsyncd.secrets
[validation]
path = /var/net/validation
uid = root
gid = root
read only = no
list = false
auth users = sync
From the client, also Fedora Core 2, also running 2.6.2-1 I'm doing the
following:
rsync -avH --delete-excluded --delete \
--password-file=/etc/rsyncval.pwd \
FOCUS sync@192.168.13.252::validation
The output is as follows:
building file list ... done
rsync: connection unexpectedly closed (69 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(342)
I don't think it is a failed authorization because it would tell me that
in the log file on the server. It seems to be getting the connection,
building a list of files to transfer, but then dies when it actually
starts to do anything.
I'd appreciate any help debugging this - I've been looking at it for
several hours now.
Thanks
Hi,
I'm sure I'm missing something simple but I can't find it.
We just set up a new server with Fedora Core 2 and I'm trying to set up
an rsync to it. I've had this working to a Debian machine, so I'm
almost sure my config is rsync config is good.
I'm running rsync 2.6.2-1 in daemon mode on the server with the
following config file:
log file = /var/log/rsyncd.log
hosts allow = 172.16.0.0/255.255.0.0
secrets file = /etc/rsyncd.secrets
[validation]
path = /var/net/validation
uid = root
gid = root
read only = no
list = false
auth users = sync
From the client, also Fedora Core 2, also running 2.6.2-1 I'm doing the
following:
rsync -avH --delete-excluded --delete \
--password-file=/etc/rsyncval.pwd \
FOCUS sync at 192.168.13.252::validation
The output is as follows:
building file list ... done
rsync: connection unexpectedly closed (69 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(342)
I don't think it is a failed authorization because it would tell me that
in the log file on the server. It seems to be getting the connection,
building a list of files to transfer, but then dies when it actually
starts to do anything.
I'd appreciate any help debugging this - I've been looking at it for
several hours now.
Thanks
--
David L. Harfst Computerized Medical Systems
Senior Systems Engineer St. Louis, Missouri
mailto:harfst@cms-stl.com http://www.cms-stl.com
On Wed, Jan 26, 2005 at 12:34:02PM -0600, David L. Harfst wrote:> building file list ... done > rsync: connection unexpectedly closed (69 bytes read so far)It would probably help to upgrade the server to 2.6.3, since 2.6.2 did not pass back most errors to the client. Also, a 2.6.3 client is a little better at grabbing a remote error message when the server dies, so upgrading the local side too might help you to debug the problem. I assume you looked for errors in the rsync log file? You might also want to try setting "ulimit -c unlimited" and then running starting the rsync daemon temporarily like this: "rsync --daemon --no-detach". After running the failing client command, kill the daemon using Ctrl-C and check if it core dumped. That will at least let you figure out if the problem is one of the program crashing or not. If not, you should hopefully be able to find an error message telling you what went wrong. ..wayne..