connection reset by peer error (in server log)
dlochart at gmail.com
Wed May 10 15:21:54 GMT 2006
Ok we got the client log a minute ago and it also had a similar reset
message, here is a snippet
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown"
[sender]: Connection reset by peer (104)
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(622)
Read from remote host 22.214.171.124: Connection reset by peer
Wayne, so based on your response then this looks like an error occurring
externally between the two machines?
Ok, so maybe we can look at the switch and the network interface to see if
they are set properly i.e 100BaseT, 1000BaseT.
Any other ideas?
If I did not mention this before, it is not consistent and we have not been
able to reproduce it at will.
On 5/10/06, Wayne Davison <wayned at samba.org> wrote:
> 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).
What profits a man if he gains the whole world yet loses his soul?
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the rsync