rsync hang fixed
Just wanted to report that I reverted to using socketpairs with rsync and the latest cygwin release, and have not experienced the hangs I was getting previously. So, seems fixed! Thanks! -- Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: rsync hang fixed
Eliot Moss a écrit : Just wanted to report that I reverted to using socketpairs with rsync and the latest cygwin release, and have not experienced the hangs I was getting previously. So, seems fixed! Thanks! It works for me with version 1.7.2-2, are you using 1.7.3-1? Nicolas -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
rsync hang on large file in a set
This is to both the rsync and cygwin lists, and I regret that it is vaguer than I would like, but ... With cygwin 1.7 (latest beta) and the rsync released with it (3.0.6-1) I try to sync a couple of Gb of Thunderbird mail files. The flag settings were -avzuP plus a --chmod and some includes/excludes to control which files to move. I would repeatably get hangs on particular files, which are generally modified by appending (mail added at the end). These files (two in particular) are approximately 100Mb or a little more in size, and that seemed to have something to do with it. The hangs I speak of are where rsync and ssh spin, consuming cpu time (fan running fast!) but making no progress. Now here's the odd thing. If I kill of the rsync and ssh processes and rsync the one file by itself, it will go through. (Of course the --partial implied by -P means that I may have to transfer a lot of data :-( ). Curiously, I got the same behavior with a recent rsync head (20091129). Last night I made two changes and have not seen a hang since (though I am monitoring this, of course). One was to substitute --progress and --partial-dir for -P. The other -- which is the cygwin relevant part -- was the compile with socketpair turned off (manually in the config file). I did this because Corinna and I had found issues between socketpair and BLODA on my (Windows 7) box, which she appeared to have fixed in revisions to 1.7 The problems had to do with fork, dup, and such, not with actual data transfer AFAIK. At her request I still have the BLODA installed, and other cygwin things generally work right. I will also play with putting socketpair back in and keeping --partial-dir. But the various reports of rsync hangs, and a particular report a little while ago of busy looping in buffer transfer (and I do have -z on, might that impact?) struck me as possibly related. I am not sure how to debug this when it happens, so if there are steps I can take upon such a hang to get you better info, do enlighten me! Best wishes -- Eliot Moss == J. Eliot B. Moss, Professor http://www.cs.umass.edu/~mosswww Director, Arch. and Lang. Impl. Lab. +1-413-545-4206voice Department of Computer Science+1-413-695-4226 cell 140 Governor's Drive, Room 372+1-413-545-1249 fax University of Massachusetts at Amherstm...@cs.umass.edu email Amherst, MA 01003-9264 USA +1-413-545-2746 Laurie Downey sec'y == -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
rsync hang
The -W option tells rsync to always transfer the whole file instead of only the changed parts, so it transfers quite more bytes, but it's less CPU-intensive. On why this works the problem around for you, it's probably because it changes the use quite a bit and casually doesn't get into that hang. hmm, I'll have to try that - rsync keeps hanging on me too (and i'm not using ssh, just doing local copies) probably not my issue but worth a shot. if I try to attach strace to the rsync it hangs too, and neither can be killed by ctrl-c (INTR) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
ssh, rsync hang the PC with Spyware Doctor running
Special request: Since Spyware Doctor is part of Google Pack http://pack.google.com, its distribution is (becoming) large. IMHO, it explicitly belongs on the FAQ's BLODA list http://cygwin.com/faq/faq.using.html#faq.using.bloda. Symptoms: after several runs of ssh and/or rsync (w/ssh underneath), the PC hangs. Though the mouse still moves, eventually (all) windows quit repainting/responding and it's hung (cold boot req'd). Twist: seems to work fine from a console-based bash session, but hangs when called from anything else (e.g., make within an Eclipse session). I shutdown PCTools' Spyware Doctor (don't need to uninstall), and I haven't seen it since. With it running I get less than a dozen runs before it hangs. Cheers! -Jim -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync hang
Scott T. Marshall wrote: I have been having some errors when using rsync to copy files from a remote cygwin machine to my local cygwin machine. I read posts the cygwin web forum. I have the same hang problem in that when I try to rsync (get) files from a remote machine rsync just hangs if any directory has what seems to be 100 files. Is there any fix for this yet? The posts I saw were from April of 2006, so I don't know if the problem is now solved or not. No, unfortunately this problem is not solved. But the problem is not in rsync itself, but in the cygwin1.dll. See http://sourceware.org/ml/cygwin/2007-02/msg00643.html I have looked at that code, but it is quite difficult stuff. And I'm having trouble compiling the cygwin.dll (downloaded the 1.5.24-2 sources via setup.exe), so I can't even give it a try at this moment. Although it is not the real compilation, but generating the docs :-S But a lot of people have this problem. It becomes a FAQ. Regards, Frank -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
rsync hang
Hi Cygwin Folks, I have been having some errors when using rsync to copy files from a remote cygwin machine to my local cygwin machine. I read posts the cygwin web forum. I have the same hang problem in that when I try to rsync (get) files from a remote machine rsync just hangs if any directory has what seems to be 100 files. Is there any fix for this yet? The posts I saw were from April of 2006, so I don't know if the problem is now solved or not. Thanks in advance. Scott -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Rsync hang and test with latest snapshots
On Wed, Dec 10, 2003 at 01:45:21AM -0500, Christopher Faylor wrote: On Wed, Dec 10, 2003 at 07:24:11AM +0100, RITTER, Philippe wrote: Hello all cygwinners ! I use rsync to synchronise many server. The most of them are still running with cygwin 1.3.20 and rsync 2.5.5. Everything is running fine in this situation. But I installed cygwin 1.5.5 and rsync 2.5.6 and some problems apairs ! Rsync was hanging and stay running in the task manager. I could only kill it. I remember some mails was about this problems, and I don't remember to see any solution. As a tip from cgf, try snapshots ! So, I tested some of them, and, since the snapshot of 3.12.2003, everything is working again. (CYGWIN_NT-4.0 ara 1.5.6s(0.107/3/2) 20031203 00:23:12 i686 unknown unknown Cygwin) Thanks to Philippe for this hint, it's a solution I was lokng for for a long time. Works for me too. Wow. Someone tested a snapshot, unbidden, it fixes a problem, and they let us know about it! I think that's definitely worth a gold star. I second this. Gruss Olaf Föllinger -- Olaf Föllinger Berater S.E.S.A. Software und Systeme AG -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Rsync hang and test with latest snapshots
Hello all cygwinners ! I use rsync to synchronise many server. The most of them are still running with cygwin 1.3.20 and rsync 2.5.5. Everything is running fine in this situation. But I installed cygwin 1.5.5 and rsync 2.5.6 and some problems apairs ! Rsync was hanging and stay running in the task manager. I could only kill it. I remember some mails was about this problems, and I don't remember to see any solution. As a tip from cgf, try snapshots ! So, I tested some of them, and, since the snapshot of 3.12.2003, everything is working again. (CYGWIN_NT-4.0 ara 1.5.6s(0.107/3/2) 20031203 00:23:12 i686 unknown unknown Cygwin) Thanks very much for your great effort to make the best of two worlds (Win and *nix) Regards Philippe RITTER -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Rsync hang and test with latest snapshots
On Wed, Dec 10, 2003 at 07:24:11AM +0100, RITTER, Philippe wrote: Hello all cygwinners ! I use rsync to synchronise many server. The most of them are still running with cygwin 1.3.20 and rsync 2.5.5. Everything is running fine in this situation. But I installed cygwin 1.5.5 and rsync 2.5.6 and some problems apairs ! Rsync was hanging and stay running in the task manager. I could only kill it. I remember some mails was about this problems, and I don't remember to see any solution. As a tip from cgf, try snapshots ! So, I tested some of them, and, since the snapshot of 3.12.2003, everything is working again. (CYGWIN_NT-4.0 ara 1.5.6s(0.107/3/2) 20031203 00:23:12 i686 unknown unknown Cygwin) Thanks very much for your great effort to make the best of two worlds (Win and *nix) Wow. Someone tested a snapshot, unbidden, it fixes a problem, and they let us know about it! I think that's definitely worth a gold star. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygcheck as body or attachment (was RE: rsync hang .... )
I've used Cygwin for several years now, and have read this mailing list for quite some time. When I encountered the rsync problem, I searched mailing lists as well as Google to find the solution, couldn't find a definitive answer, and eventually found one myself that worked, so I thought I'd post it (as many other people had reported similar problems in the archives) in order to help. I almost didn't email the list with this solution because I couldn't remember whether or not to include the output of cygcheck as an attachment or as part of the body. I looked on the mailing list webpage on cygwin.com, and couldn't see any info, so I decided to put it in the body. I should have looked further, but I figured it wouldn't be a big deal. Of course, I chose the wrong way, and got flamed. I think the people I work with would think of me as a nice guy. I hope this comment doesn't get me blocked from the cygwin list ;-) Normally I ignore such things, but I felt compelled because I have seen many other messages with the following content... PLEASE include the generated files 'cygcheck.txt' *as an attachment*, and NOT in the body of the mail message. If you don't believe me visit http://cygwin.com/ml/cygwin/ and type as an attachment in the search box. I got 2862 hits. This makes me believe you've been subscribed to the mailing list for quite some time, but may not have actually read many messages. I can understand this. It's an active list. So I thought I would help by pointing this out. On the other hand, now I understand the WJM philosophy, because in this case it worked... I now know the right way. You may ask yourself why I bothered replying to this post. We'll you made another minor mistake by adding my address to email distribution list. I obviously read the mailing list and this simply resulted in me getting two copies of the same messages. I hope pointing this out doesn't seem too mean. Imagine if you would have done this to cfg! Anyway, I hope that my simple patch can help someone else in the future, and if the additional body of my message bothered anyone, I apologize. I hope you helped someone too. I'm sure you did. Just ignore the mean people on the list, but use their advice to avoid further meanness. Pete -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygcheck as body or attachment (was RE: rsync hang .... )
I'm just a user and follower of cygwin, but it amazes me how many people put the output of cygcheck -s output: or cygcheck -svr in the body of their email instead of as an attachment when every stinking email has http://cygwin.com/problems.html at the bottom of it and that page has Run cygcheck -s -v -r cygcheck.out and include that as an attachment in your report. I've used Cygwin for several years now, and have read this mailing list for quite some time. When I encountered the rsync problem, I searched mailing lists as well as Google to find the solution, couldn't find a definitive answer, and eventually found one myself that worked, so I thought I'd post it (as many other people had reported similar problems in the archives) in order to help. I almost didn't email the list with this solution because I couldn't remember whether or not to include the output of cygcheck as an attachment or as part of the body. I looked on the mailing list webpage on cygwin.com, and couldn't see any info, so I decided to put it in the body. I should have looked further, but I figured it wouldn't be a big deal. Of course, I chose the wrong way, and got flamed. I now know the right way. Anyway, I hope that my simple patch can help someone else in the future, and if the additional body of my message bothered anyone, I apologize. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin/rsync Hang Problem Testing Results
Paul Thompson wrote: People of cygwin rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a get (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going to work. So I searched the web, mailing lists, etc, and came across all of the posts on the subject, but no solution. Then I stumbled across an idea - to test previous versions of rsync to if any of them worked better with cygwin. Here are the (hopefully helpful) results of those tests. I did three tests for each version of cygwin: snip So, based on my testing, I would conclude that the infamous cygwin rsync hang bug was introduced somewhere in the coding for 2.4.6. As for myself, I plan to go ahead and just use version 2.4.0, as it is the most recent version of rsync that worked for all three tests. If I can be of any more help, including testing patches, please let me know. I tried 2.4.0 and seemed to work for a while, but now with more differences to transfer I have encountered the connection reset by peer error with this version also. Perhaps the subsequent changes didn't introduce the bug but merely changed the circumstances in which it appears (very easy if it is threading related). Regards, Mark Thornton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin/rsync Hang Problem Testing Results
Mark Thornton wrote: So, based on my testing, I would conclude that the infamous cygwin rsync hang bug was introduced somewhere in the coding for 2.4.6. As for myself, I plan to go ahead and just use version 2.4.0, as it is the most recent version of rsync that worked for all three tests. If I can be of any more help, including testing patches, please let me know. Can you suggest a download source for 2.4.0? I have only been able to find 2.4.6, 2.5.6-1 and 2.5.6-2. By the way were either of your machines dual processors (or hyperthreaded)? rsync ftp site - http://rsync.samba.org/ftp/rsync/old-versions/rsync-2.4.0.tar.gz http://rsync.samba.org/ftp/rsync/old-versions/ And one of my machines is dual processored. However, the machine that I did all of my testing on was a normal Pentium-4 laptop. No hyperthreading, I think... Paul -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin/rsync Hang Problem Testing Results
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Thompson wrote:
| 2.4.5 success success 2.4.6 failure failure
Funny this is: 2.4.6 is exactly the release where many cygwin-related
patches landed in rsync code, as I'm seeing from a diff.
(I began packaging rsync on CygWin at 2.4.6 and I never had your good
idea to test older versions too, what a chanche it is that 2.4.5 is the
first working one!)
I attach an purposedly incomplete diff between sources of 2.4.5 and
2.4.6 (I removed 'uninteresting' changes such as configure script
changing line numbers...)
[Most notable difference is the addiction of shutdown and the lowering
of the sleep time.]
- --
Lapo 'Raist' Luchini
[EMAIL PROTECTED] (PGP X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAj9+atwACgkQaJiCLMjyUvuHMACeJjK59CeZrpe1/eWuiUloZd5Q
Y7MAoLr3BjhtJXRNfaYAMD6ReAZ/1mVp
=712L
-END PGP SIGNATURE-
--- rsync-2.4.5/authenticate.c 2000-01-23 03:16:51.0 +0100
+++ rsync-2.4.6/authenticate.c 2000-08-19 17:25:05.0 +0200
@@ -135,7 +135,6 @@
static char *getpassf(char *filename)
{
char buffer[100];
- int len=0;
int fd=0;
STRUCT_STAT st;
int ok = 1;
@@ -170,7 +169,7 @@
if (envpw) rprintf(FERROR,RSYNC_PASSWORD environment variable ignored\n);
buffer[sizeof(buffer)-1]='\0';
- if ( (len=read(fd,buffer,sizeof(buffer)-1)) 0)
+ if (read(fd,buffer,sizeof(buffer)-1) 0)
{
char *p = strtok(buffer,\n\r);
close(fd);
diff -bu rsync-2.4.5/clientserver.c rsync-2.4.6/clientserver.c
--- rsync-2.4.5/clientserver.c 2000-08-04 23:26:17.0 +0200
+++ rsync-2.4.6/clientserver.c 2000-08-29 06:47:08.0 +0200
@@ -38,6 +38,11 @@
extern int am_sender;
extern struct in_addr socket_address;
+ if (argc == 0 !am_sender) {
+ extern int list_only;
+ list_only = 1;
+ }
+
if (*path == '/') {
rprintf(FERROR,ERROR: The remote path must start with a module
name\n);
return -1;
diff -bu rsync-2.4.5/configure rsync-2.4.6/configure
--- rsync-2.4.5/configure 2000-04-19 07:33:39.0 +0200
+++ rsync-2.4.6/configure 2000-09-06 01:21:27.0 +0200
@@ -525,6 +525,7 @@
# compile with optimisation and without debugging by default
CFLAGS=${CFLAGS--O}
+LDFLAGS=${LDFLAGS-}
ac_aux_dir=
for ac_dir in $srcdir $srcdir/.. $srcdir/../..; do
@@ -654,10 +655,46 @@
ac_cv_target_system_type=$target
+# look for getconf early as this affects just about everything
+# Extract the first word of getconf, so it can be a program name with args.
+set dummy getconf; ac_word=$2
+echo $ac_n checking for $ac_word... $ac_c 16
+echo configure:663: checking for $ac_word 5
+if eval test \`echo '$''{'ac_cv_prog_HAVE_GETCONF'+set}'`\ = set; then
+ echo $ac_n (cached) $ac_c 16
+else
+ if test -n $HAVE_GETCONF; then
+ ac_cv_prog_HAVE_GETCONF=$HAVE_GETCONF # Let the user override the test.
+else
+ IFS=${IFS= }; ac_save_ifs=$IFS; IFS=:
+ ac_dummy=$PATH
+ for ac_dir in $ac_dummy; do
+test -z $ac_dir ac_dir=.
+if test -f $ac_dir/$ac_word; then
+ ac_cv_prog_HAVE_GETCONF=1
+ break
+fi
+ done
+ IFS=$ac_save_ifs
+ test -z $ac_cv_prog_HAVE_GETCONF ac_cv_prog_HAVE_GETCONF=0
+fi
+fi
+HAVE_GETCONF=$ac_cv_prog_HAVE_GETCONF
+if test -n $HAVE_GETCONF; then
+ echo $ac_t$HAVE_GETCONF 16
+else
+ echo $ac_tno 16
+fi
+
+if test $HAVE_GETCONF = 1; then
+ CFLAGS=$CFLAGS `getconf LFS_CFLAGS`
+ LDFLAGS=$LDFLAGS `getconf LFS_LDFLAGS`
+fi
+
# Extract the first word of gcc, so it can be a program name with args.
set dummy gcc; ac_word=$2
echo $ac_n checking for $ac_word... $ac_c 16
-echo configure:661: checking for $ac_word 5
+echo configure:698: checking for $ac_word 5
if eval test \`echo '$''{'ac_cv_prog_CC'+set}'`\ = set; then
echo $ac_n (cached) $ac_c 16
else
@@ -3502,6 +3540,7 @@
[EMAIL PROTECTED]@%$build_cpu%g
[EMAIL PROTECTED]@%$build_vendor%g
[EMAIL PROTECTED]@%$build_os%g
[EMAIL PROTECTED]@%$HAVE_GETCONF%g
[EMAIL PROTECTED]@%$CC%g
[EMAIL PROTECTED]@%$INSTALL_PROGRAM%g
[EMAIL PROTECTED]@%$INSTALL_SCRIPT%g
diff -bu rsync-2.4.5/configure.in rsync-2.4.6/configure.in
--- rsync-2.4.5/configure.in2000-04-19 07:33:39.0 +0200
+++ rsync-2.4.6/configure.in2000-09-06 01:21:27.0 +0200
@@ -4,15 +4,24 @@
# compile with optimisation and without debugging by default
CFLAGS=${CFLAGS--O}
+LDFLAGS=${LDFLAGS-}
AC_CANONICAL_SYSTEM
AC_VALIDATE_CACHE_SYSTEM_TYPE
+# look for getconf early as this affects just about everything
+AC_CHECK_PROG(HAVE_GETCONF, getconf, 1, 0)
+if test $HAVE_GETCONF = 1; then
+ CFLAGS=$CFLAGS `getconf LFS_CFLAGS`
+ LDFLAGS=$LDFLAGS `getconf LFS_LDFLAGS`
+fi
+
dnl Checks for programs.
AC_PROG_CC
Cygwin/rsync Hang Problem Testing Results
People of cygwin rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a get (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going to work. So I searched the web, mailing lists, etc, and came across all of the posts on the subject, but no solution. Then I stumbled across an idea - to test previous versions of rsync to if any of them worked better with cygwin. Here are the (hopefully helpful) results of those tests. I did three tests for each version of cygwin: locallist: rsync -n --stats --recursive --rsh=ssh sync/ /home/drsync/ get: RSYNC_CMD=rsync --verbose --progress --stats -auz -e ssh $RSYNC_CMD [EMAIL PROTECTED]:sync/ sync/ put: RSYNC_CMD=rsync --verbose --progress --stats -auz -e ssh $RSYNC_CMD sync/ [EMAIL PROTECTED]:sync/ When rsync was hanging, it did so usually by the third time I ran the command. So I figured running each 10ish times should probably show the error. So I downloaded the last pile of rsync releases and started testing at intervals, starting back at 2.3.0 and splitting the difference as I zeroed in on the offending release. Here are the results: Version locallist get put --- 2.3.0 success success success 2.4.0 success success success 2.4.1 success success failure 2.4.2 success success failure 2.4.3 success success failure 2.4.4 success success failure 2.4.5 success success failure 2.4.6 failure failure failure 2.5.0 failure failure success 2.5.6 failure failure success The failures of the put test (v. 2.4.1 - 2.4.6) happened EVERY time I ran the test and returned an error of: read error: Connection reset by peer As those did not occur after 2.4.6, I assume that was a fixed bug, unrelated to the hanging problem that was the reason for my tests. Anyhow, when the locallist and get tests failed, rsync would just plain hang - no explanation, error, I could leave it there for an hour and it wouldn't have changed. And then, when I ctrl-c killed the process (in my cygwin/bash shell), the actual rsync process would stick around and require killing via the windows task manager. So, based on my testing, I would conclude that the infamous cygwin rsync hang bug was introduced somewhere in the coding for 2.4.6. As for myself, I plan to go ahead and just use version 2.4.0, as it is the most recent version of rsync that worked for all three tests. If I can be of any more help, including testing patches, please let me know. Thanks for all of the hard work on cygwin and rsync, folks. Sincerely, Paul Thompson [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin/rsync Hang Problem Testing Results
I have found rsync runs slighty longer when you run ssh -e 'noescape' option, as in the following script: #!/bin/bash exec ssh -e 'none' $@ In fact, I find the above script is absolutely essential with cvs. (I've yet to platform where it wasn't required.) One would expect the -T option to also improve things, but it doesn't... I find it helps with rsync, but doesn't solve the problem. Worse, each time rsync hangs, after killing it, the rsync process continues on the remote machine. If I don't manually kill -9 rsync on the remote machine, the next time I run rsync it will hang sooner and run slower. After five or ten times without killing the remote rsync command, rsync never gets past update the filelist before I grow too impatient to see what will happen. Bill - Original Message - From: Paul Thompson [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 02, 2003 7:28 PM Subject: Cygwin/rsync Hang Problem Testing Results People of cygwin rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a get (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going to work. So I searched the web, mailing lists, etc, and came across all of the posts on the subject, but no solution. Then I stumbled across an idea - to test previous versions of rsync to if any of them worked better with cygwin. Here are the (hopefully helpful) results of those tests. I did three tests for each version of cygwin: locallist: rsync -n --stats --recursive --rsh=ssh sync/ /home/drsync/ get: RSYNC_CMD=rsync --verbose --progress --stats -auz -e ssh $RSYNC_CMD [EMAIL PROTECTED]:sync/ sync/ put: RSYNC_CMD=rsync --verbose --progress --stats -auz -e ssh $RSYNC_CMD sync/ [EMAIL PROTECTED]:sync/ When rsync was hanging, it did so usually by the third time I ran the command. So I figured running each 10ish times should probably show the error. So I downloaded the last pile of rsync releases and started testing at intervals, starting back at 2.3.0 and splitting the difference as I zeroed in on the offending release. Here are the results: Version locallist get put --- 2.3.0 success success success 2.4.0 success success success 2.4.1 success success failure 2.4.2 success success failure 2.4.3 success success failure 2.4.4 success success failure 2.4.5 success success failure 2.4.6 failure failure failure 2.5.0 failure failure success 2.5.6 failure failure success The failures of the put test (v. 2.4.1 - 2.4.6) happened EVERY time I ran the test and returned an error of: read error: Connection reset by peer As those did not occur after 2.4.6, I assume that was a fixed bug, unrelated to the hanging problem that was the reason for my tests. Anyhow, when the locallist and get tests failed, rsync would just plain hang - no explanation, error, I could leave it there for an hour and it wouldn't have changed. And then, when I ctrl-c killed the process (in my cygwin/bash shell), the actual rsync process would stick around and require killing via the windows task manager. So, based on my testing, I would conclude that the infamous cygwin rsync hang bug was introduced somewhere in the coding for 2.4.6. As for myself, I plan to go ahead and just use version 2.4.0, as it is the most recent version of rsync that worked for all three tests. If I can be of any more help, including testing patches, please let me know. Thanks for all of the hard work on cygwin and rsync, folks. Sincerely, Paul Thompson [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync hang - strace output - any ideas?
Max Bowsher wrote: I was running the rsync testsuite, and an rsync process hung. I did strace -p pid, and got 1 line of trace: 4 4 [sig] rsync 2540 wait_sig: looping Does this mean anything to any Cygwin gurus? What release are you using exactly? In 2.5.5-2 I added a small patch (don't remember the author, see the included README) that adds a sleepms(30) to try to avoid a (possible?) bug in signaling between parent and child in Cygwin. Some heavy user say that also with that sleepms(30) they sometime hang and that sleepms(100) relsolved that better, but this degrades performances. The imminent 2.5.6 adds a cache in the network stream that shuold help and some other fixes (not by me). For more infos: http://www.mail-archive.com/rsync@lists.samba.org/ -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync hang - strace output - any ideas?
Lapo Luchini wrote: Max Bowsher wrote: [...] For more infos: http://www.mail-archive.com/rsync@lists.samba.org/ Ops! I didn't notice it was you I was answering to... of course you know that ML fairly well, as you post in it daily ;-) -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync hang - strace output - any ideas?
Lapo Luchini wrote: Max Bowsher wrote: I was running the rsync testsuite, and an rsync process hung. I did strace -p pid, and got 1 line of trace: 4 4 [sig] rsync 2540 wait_sig: looping Does this mean anything to any Cygwin gurus? What release are you using exactly? 2.5.6 In 2.5.5-2 I added a small patch (don't remember the author, see the included README) that adds a sleepms(30) to try to avoid a (possible?) bug in signaling between parent and child in Cygwin. Some heavy user say that also with that sleepms(30) they sometime hang and that sleepms(100) relsolved that better, but this degrades performances. I ran the rsync testsuite in a loop, and eventually got a hang, gdb-ed it, got the backtrace and posted it here ([EMAIL PROTECTED]). Based on that, I do not think that the signalling between parent and child is at fault. As best I can tell, something is going wrong in socketpair_tcp(), causing rsync to end up blocked on accept(). It's probably some peculiarity of Winsock. PS: Did you catch my message regarding pipe vs. socketpair? It might be an idea to use pipe in 2.5.6-1 unless we can figure out why Cygwin's socketpair doesn't always work. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync hang - strace output - any ideas?
Max Bowsher wrote: I got this from gdb: (gdb) bt #0 0x77f767ce in ?? () i.e. nothing useful. If anyone has any suggestions for getting more info, please say. I posted a script to this list some time back that can be used to translate NT addresses (like the 0x77f767ce above) to function names. This can be a help in understanding what a thread is hanging on. There were two versions of the script. The first one just dumps a list, the second one was enhanced with a cache and could spit out the names of the nearest function(s). -- Joe Buehler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync hang - strace output - any ideas?
On Wed, Jan 29, 2003 at 01:13:33PM -0500, Joe Buehler wrote: Max Bowsher wrote: I got this from gdb: (gdb) bt #0 0x77f767ce in ?? () i.e. nothing useful. If anyone has any suggestions for getting more info, please say. I posted a script to this list some time back that can be used to translate NT addresses (like the 0x77f767ce above) to function names. This can be a help in understanding what a thread is hanging on. The newly released version of gdb may do this automatically. I accidentally included a patch from the net in this version which added this functionality. I meant to remove it because it was rumored to have problems but it seems to be working ok, AFAICT. When doing backtraces, please remember that thread 1 is the main thread. Usually that is the thread which is doing something interesting. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync hang - strace output - any ideas?
On Wed, Jan 29, 2003 at 07:41:27PM -, Max Bowsher wrote: Christopher Faylor wrote: On Wed, Jan 29, 2003 at 01:13:33PM -0500, Joe Buehler wrote: Max Bowsher wrote: I got this from gdb: (gdb) bt #0 0x77f767ce in ?? () i.e. nothing useful. If anyone has any suggestions for getting more info, please say. I posted a script to this list some time back that can be used to translate NT addresses (like the 0x77f767ce above) to function names. This can be a help in understanding what a thread is hanging on. The newly released version of gdb may do this automatically. I accidentally included a patch from the net in this version which added this functionality. I meant to remove it because it was rumored to have problems but it seems to be working ok, AFAICT. Yes, it's working fine for me. Unless it really messes up, can you leave it in? There is a newer, better patch coming. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
rsync hang - strace output - any ideas?
I was running the rsync testsuite, and an rsync process hung. I did strace -p pid, and got 1 line of trace: 4 4 [sig] rsync 2540 wait_sig: looping Does this mean anything to any Cygwin gurus? I got this from gdb: (gdb) bt #0 0x77f767ce in ?? () i.e. nothing useful. If anyone has any suggestions for getting more info, please say. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
