similar to: rsync crash

rsync 2.5.0 still has a bug where it hangs under some circumstances. The hang is beyond my abilities to track down. I'll keep trying, though, but here are details in case they're of use to anyone else: - Code configured & built on Solaris 2.5.1. - Same binary run on Solaris 2.5.1 (client) and 2.8 (server). - Using rsh transport, but also fails with ssh - Does not fail with

https://bugzilla.samba.org/show_bug.cgi?id=5701 Summary: deadlock on local rsyncing, bisected to commit f303b749f2843433c9acd8218a4b9096d0d1bb8d Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

Hi, In http://sources.redhat.com/ml/cygwin/2002-09/msg01155.html, I noted that the often-observed hangs of rsync under Cygwin were assuaged by a call to msleep(). After upgrading my Cygwin environment to rsync 2.5.6, I'm seeing these hangs again, not surprisingly given a CVS entry for main.c notes that this kludge was not harmless: Revision 1.162 / (download) - annotate - [select for

Hi, I am using rsync 2.6.9 and recently I got a error with the setup. I searched in the forums but I couldn't find much clues on this. Once I restarted the rsync daemon and rerunning the job didn't gave any errors further. I also tried to reproduce the issue for much details. But I couldn't do that even after hours. The rsync log says opening tcp connection to 172.21.3.148

I'm using rsync 2.6.9 under Solaris 10. The file system I'm trying to sync has ~7.6 million files. Here's what happens: # rsync -avS . /newfiles1 building file list ... done rsync: fork failed in do_recv: Not enough space (12) rsync error: error in IPC code (code 14) at main.c(709) [receiver=2.6.9] rsync: connection unexpectedly closed (8 bytes received so far) [sender] rsync error:

I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes. It dumps core when preserve_hard_links and backup. And SUPPORT_HARD_LINKS is true. rsync -avH --delete --backup --backup-dir=/some/backup/dir \ srchost::dir/ dir/ The core says... ------------------------------------------------------------------------ Program terminated with signal 11, Segmentation fault. #0 0x80536c0 in keep_backup

Greetings and salutations, rsync users. I have a problem. I'm hoping that someone out there could perhaps provide a hand. I've been trying to transfer large amounts of data (lots of data, lots of files) via rsync over an encrypted TCP tunnel, but I seem to be continually getting hangs in the transfers -- things will go along for a bit, and then just come to a screetching halt. There

Hi, if socketpair support has been compiled in but the host where rsync is run doesn't support it, you get error pipe failed in do_recv This patch makes rsync use pipe if socketpair fails. Yours, Harri J?rvi CC me if you reply to this thread since I'm not on the mailing list -------------- next part -------------- --- rsync-2.5.5/util.c Wed Mar 20 03:09:49 2002 +++ util.c Thu Jul 24

Hi, I'm running the latest cygwin, with rsync 2.6.6 protocol 26. My command is: c:\cygwin\bin\rsync -vrtz --delete /cygdrive/e phoenix@172.16.1.10 etc I get the following error when trying to rsync 500,000 files: rsync: fork failed in do_recv: Cannot allocate memory (12) rsync error: error in IPC code (code 14) at main.c(550) rsync: connection unexpectedly closed (4 bytes received so

On Mon, Sep 23, 2002 at 01:06:22PM -0700, Sudheer Tumuluru wrote: > > I am having the same problem with rsync 2.5.5-1. I am > trying to rsync a couple of short text files between a linux server and > Win2k Professional boxes with cygwin. About 20% of the time, rsync freezes > at the end of the transfer, and I can't kill the rsync process in > cygwin even if I give it a 9

Rsync list: Alberto and I have done a couple more exchanges by private email, and we found that he wasn't turning on my include/exclude optimization in his test because he had an "exclude" directive in rsyncd.conf. He has now removed that and run the test again. His very interesting results are below with my comments. Note that his case is rather pathological because he's got

Hey guys, I've been working with rsync for the last couple weeks and I really need some help here. Linux to Linux transfers are working beautifully, but for the life of me I can't get transfers from win2k to work. I have the exact problem that was reported by Mark de Jong on Tue, 16 Jul 2002. I'm using the lastest version of cygwin, with rsync 2.5.5 and ssh 3.5p1 for my tests. The

https://bugzilla.samba.org/show_bug.cgi?id=4139 Summary: Generator process (running as daemon) hangs after kill SIGINT. Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=5020 Summary: hang using RSYNC_CONNECT_PROG Product: rsync Version: 3.0.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: Matt_Domsch@dell.com QAContact:

Hi all. I once tried to rsync around 100 GB (10 million files), but version 2.6.6 needed too much RAM and was too slow. Is one of the snapshots stable enough to try this again? Greetings Sven -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url :

[This is a copy of the contents of Debian bug report #147842.] Package: rsync Version: 2.5.5-0.2 Severity: normal Cause ----- - rsync forks a child which in turn forks a grandchild in main.c:do_recv(). - Diagnostics written by the grandchild need to be read by the child using read_error_fd() to be handled properly (with the end result being that they are seen by the user running rsync). -

Hi everybody, I use rsync v2.5.5 almost without problems, but it dumps core from time to time. Core was generated by `rsync'. Program terminated with signal 11, Segmentation fault. There is excerpt from gdb's bt: #0 0x2810106f in __sfvwrite () from /usr/lib/libc.so.4 #1 0x280fdfe1 in fprintf () from /usr/lib/libc.so.4 #2 0x281002b6 in vfprintf () from /usr/lib/libc.so.4 #3

Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a

Hello, I'm trying to get RSync to work between an NT workstation and a Win98 workstation. Has anybody gotten this to work? I know my NT workstation is set up correctly because I am able to RSync between two NT workstations. But when I try to RSync between an NT and Win98 workstation I get a "pipe failed on do_recv" with an RSync exit status of 10. My NT workstation is set up to

Hello everyone, Here is the scenario: I have an rsync daemon on server P and a script on server H. The source is server P. Files are copied from P to H. I noticed that when the script is run, there are 2 instances of rsync running (using ps) on server H. Is this normal behaviour? My rsync command is: rsync -rlpogt --delete-after --exclude-from=$EXCLUDESFILE --temp-dir=/tmp --stats $1 $2