rsync - Feb 2005 - [Bug 2328] cygwin rsync hangs when initiated remotely after transfering some files

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


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Additional Comments From wayned@samba.org  2005-02-25 17:02 -------
If you could try commenting out HAVE_SOCKETPAIR from config.h and re-compiling
rsync, it would be nice to know if that makes rsync stop hanging.  If you
don't
have the cygwin source, you should be able to use their setup.exe tool to grab
it and build it using their patches (such as the one to open temp files in
binary mode).

-- 
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.

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





------- Additional Comments From bugzilla@cale.cc  2005-03-05 20:19 -------
(In reply to comment #0)
See also http://www.cygwin.com/ml/cygwin/2003-10/msg00129.html

-- 
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.

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





------- Additional Comments From cfinley@u.washington.edu  2005-03-10 16:05
-------
Created an attachment (id=1024)
 --> (https://bugzilla.samba.org/attachment.cgi?id=1024&action=view)
rsync compile on cygwin with HAVE_SOCKETPAIR commented from config.h


-- 
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.

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





------- Additional Comments From cfinley@u.washington.edu  2005-03-10 16:01
-------
After commenting out HAVE_SOCKETPAIR, the behavior remained similar: rsync
started remotely over ssh transfered a few files and then froze. It looks like
it transfered the file differences still.

runtests.sh failed on the deamon test while compiling. Attached is the compile
output. I just tried initiating rsync using ssh.

(In reply to comment #1)
> If you could try commenting out HAVE_SOCKETPAIR from config.h and
re-compiling
[...snip...]

-- 
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.

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





------- Additional Comments From cfinley@u.washington.edu  2005-03-10 16:19
-------
What is working:
I have rsyncd running from a startup batch file on Windows/cygwin:
c:\cygwin\bin\rsync.exe --config=/cygdrive/c/cygwin/etc/rsyncd/rsyncd.conf
--daemon --no-detach --address localhost

SSHD is running as a service using cygrunsrv.

Trying to run rsyncd as a service gives me "event: rsyncd : PID 1468 :
starting
service `rsyncd' failed: signal 11 raised." - is there a way to get
better
information on the error?

rsync on the Linux backup server can use the SSH tunnel to the windows machine
connecting to the rsyncd deamon and successfully backup the "Module".
It works
on about 3GB of files (fails on the Windows registry files as suspected).

-- 
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.

My belief is that rsync over ssh is tickling a deadlock
race condition in cygwin.

See this message and trace it backwards for more context:
  http://cygwin.com/ml/cygwin-patches/2005-q1/msg00015.html

I have recently re-volunteered to the author to help out getting his
patches tested but have heard nothing yet.

If this is the cause, then it is deep in cygwin.

Note that one possible workaround is to "push" from the
Windows system rather than to "pull" it from another system.
Not always possible.

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





------- Additional Comments From jek-samba@kleckner.net  2005-03-17 00:22
-------
My belief is that rsync over ssh is tickling a deadlock
race condition in cygwin.

See this message and trace it backwards for more context:
 http://cygwin.com/ml/cygwin-patches/2005-q1/msg00015.html

I have recently re-volunteered to the author to help out getting his
patches tested but have heard nothing yet.

If this is the cause, then it is deep in the cygwin
interaction with some ill-defined system calls for queues.

Note that one possible workaround is to "push" from the
Windows system rather than to "pull" it from another system,
although this is not always possible because of firewalls.

-- 
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.

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





------- Additional Comments From wayned@samba.org  2005-03-17 02:11 -------
I certainly suspected that this was a problem in the cygwin pipe/socketpair
handling.  Thanks for the extra testing Chris, and for the work on getting this
fixed in cygwin Jim!

-- 
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.

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


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |LATER




------- Additional Comments From wayned@samba.org  2005-03-18 19:40 -------
I'm marking the cygwin hang bugs as "LATER" because this is a bug
is in the
cygwin pipe code, so it is outside rsync's control.  We'll revisit this
issue
later after we hear that the cygwin code has been fixed.

I wonder if specifying a --bwlimit might work around the problem by ensuring
that the pipes can't fill up enough to deadlock.  While we're waiting
for a
cygwin fix, give that a try.

-- 
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.

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





------- Additional Comments From cfinley@u.washington.edu  2005-03-18 23:35
-------
I tried the bandwidth limit option with the same lock-up behavior. I think I had
the setting down to 8 (8KB/s?).

Is there a thread or bug reference with CYGWIN?

-- 
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.

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





------- Additional Comments From jek-samba@kleckner.net  2005-03-22 11:26
-------
(In reply to comment #9)
> Is there a thread or bug reference with CYGWIN?
The previously mentioned link is the best reference:
 http://cygwin.com/ml/cygwin-patches/2005-q1/msg00015.html 
Cygwin seems to only sort of use bugzilla.  The community
prefers to use the various mailing lists to track and work
things out.

-- 
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.