[Bug 2208] cygwin version of rsync sometimes hangs

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=2208





------- Additional Comments From bmueller at rentmanager.com  2005-01-18 13:36 -------
I am having a very similar problem.  Possibly my comments can crack this issue.

Using several different servers.  Slackware with rsync 2.6.3 and FreeBSD 5.2.1 
with rsync 2.6.3 and clients (several) running cygwin 1.5.12(0.116/4/2) on 
various versions of windows.

My testbed systems are Windows XP Pro SP2 and a Windows 2003 Server System.  I 
am trying to backup these systems to any one of the rsync servers.

My command on the client is:

C:\rsync\rsync.exe --compress --delete --ignore-errors --recursive --verbose --
times --modify-window=5 --stats --
progress '/cygdrive/C/' 'username at host.server.com::share_name/test_server/test_
set/C/'

What seems to happen is that transfer will stop on the client at some point in 
time (say 2:00am) and then the client and the server will both get errors 
about an hour later.  The client gets

rsync: writefd_unbuffered failed to write 16385 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 /home/lapo/packaging/tmp/rsync-2.6.3/io.c(515)

The server gets...

rsync: writefd_unbuffered failed to write 43 bytes: phase "unknown" 
[generator]: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(915)

Looking at these it would seem that at some point the client and server simply 
stop communicating even though they are still connected.  Possibly a network 
hiccup happened in the middle of a transfer, didn't see anything obvious in 
minitoring the nextowrk.  They then enter this "unknown" state and while they 
are there they hang out for 1 hour or so - during this time they appear to 
think they are still connected.  After this time they both die with the above 
errors.

This is not specific to any fileset or any specific file.  It might happen 
after running for several days, or after a few minutes.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.