connection reset by peer error (in server log)

Wayne Davison wayned at
Wed May 10 15:13:40 GMT 2006

On Wed, May 10, 2006 at 02:35:47PM +0000, Doug Lochart wrote:
> Can anyone shed some light on this error we are getting or know of a
> way to find out more info?

As explained on the issues and debugging page of the rsync website, a
closed connection tells us nothing about what has happened to cause the
socket to close -- it could be that the socket failed due to a network
error, or it could be that the rsync on the other end of the connection
died unexpectedly.  Since this is the server side that is logging these
messages, it should be fairly easy for you to check what the client side
is reporting -- does it output any errors?  If it also outputs something
about an unexpectedly closed connection, then the failure is probably
caused by outside forces that rsync can't control.  If it is something
like the "unexpected tag 3" error, there is a fix for that posted to the
mailing list (and already committed to CVS).


More information about the rsync mailing list