Can anyone shed some light on this error we are getting or know of a way to find out more info? Thanks in advance for any help ... we are puzzled. Our server is Linux, rsync version 2.6.7 running in daemon mode Our clients are windows; using cwrsync version 2.6.7 Our method of transport is opening an SSH tunnel then doing rsync through it. We have tested this internally and it has worked very well. We are now testing at 2 other sites and we are now getting these errors. One client is using 128k uplink the other has T1 2006/05/09 20:29:58 [16550] rsync: read error: Connection reset by peer (104) 2006/05/09 20:29:58 [16550] rsync error: error in rsync protocol data stream (code 12) at io.c(622) [receiver] 2006/05/09 20:29:58 [16550] rsync: connection unexpectedly closed (140862 bytes received so far) [generator] 2006/05/09 20:29:58 [16550] rsync error: error in rsync protocol data stream (code 12) at io.c(471) [generator] 2006/05/09 20:42:22 [16559] recv localhost.localdomain [127.0.0.1] ClipperCity () cygdrive/C/Documents and Setting\ s/Administrator/My Documents/Clipper City Brewing Co_, L_P_-050906.ptb20992988 2006/05/09 20:42:23 [16559] recv localhost.localdomain [127.0.0.1] ClipperCity () cygdrive/C/Documents and Setting\ s/Administrator/My Documents/Return.doc 20480 2006/05/09 20:42:23 [16559] sent 28 bytes received 41955834 bytes total size 1727648754 2006/05/09 22:22:46 [16530] rsync: connection unexpectedly closed (90561973 bytes received so far) [receiver] 2006/05/09 22:22:46 [16530] rsync error: error in rsync protocol data stream (code 12) at io.c(471) [receiver] 2006/05/09 22:22:46 [16530] rsync: writefd_unbuffered failed to write 87 bytes: phase "unknown" [generator]: Broke\ n pipe (32) 2006/05/09 22:22:46 [16530] rsync error: error in rsync protocol data stream (code 12) at io.c(1126) [generator] And another one (earlier) .... sent 28 bytes received 30323539 bytes total size 30290991 2006/05/09 05:24:43 [15354] rsync: connection unexpectedly closed (117974872 bytes received so far) [receiver] 2006/05/09 05:24:43 [15354] rsync error: error in rsync protocol data stream (code 12) at io.c(471) [receiver] 2006/05/09 05:24:43 [15354] rsync: writefd_unbuffered failed to write 87 bytes: phase "unknown" [generator]: Broke\ n pipe (32) 2006/05/09 05:24:43 [15354] rsync error: error in rsync protocol data stream (code 12) at io.c(1126) [generator] 2006/05/09 05:58:41 [15403] rsync: connection unexpectedly closed (5851105 bytes received so far) [receiver] 2006/05/09 05:58:41 [15403] rsync error: error in rsync protocol data stream (code 12) at io.c(471) [receiver] 2006/05/09 05:58:41 [15403] rsync: writefd_unbuffered failed to write 87 bytes: phase "unknown" [generator]: Broke\ n pipe (32) 2006/05/09 05:58:41 [15403] rsync error: error in rsync protocol data stream (code 12) at io.c(1126) [generator] Doug -- What profits a man if he gains the whole world yet loses his soul? -------------- next part -------------- HTML attachment scrubbed and removed
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). ..wayne..