Dear All, I've been using rsync since almost 1 year to synchronise 2 RHEL 3 servers. Everything has been running fine until a few weeks ago. I'm getting the following error message via crond: rsync: fork failed in do_recv: Cannot allocate memory (12) rsync error: error in IPC code (code 14) at main.c(552) Here is part of the log: 2005/12/04 03:35:54 [4345] rsync on Prod/ from mirror.company.com (10.0.0.16) 2005/12/04 03:56:52 [4337] sent 17599277 bytes received 467 bytes total size 144263481292 2005/12/04 23:06:55 [4345] rsync: connection unexpectedly closed (465 bytes received so far) [sender] 2005/12/04 23:06:55 [4345] rsync error: error in rsync protocol data stream (code 12) at io.c(434) 2005/12/04 23:06:55 [4345] rsync: writefd_unbuffered failed to write 76 bytes: phase "unknown" [sender]: Broken pipe (32) 2005/12/04 23:06:55 [4345] rsync error: error in rsync protocol data stream (code 12) at io.c(1099) I'm using rsync version 2.6.5 protocol version 29. The same script runs for other modules but rsync always seems to fail/crash for one particular module. Please note that everything was running file before, even for this module. All the module parameters are identical. I suspect the reason being the very large number of files in that module. Can anyone help me find the cause of the problem and hopefully the solution? -------------- next part -------------- HTML attachment scrubbed and removed
Dear all, I've been using rsync since almost 1 year to synchronise 2 RHEL 3 servers. Everything has been running fine until a few weeks ago. I'm getting the following error message via crond: rsync: fork failed in do_recv: Cannot allocate memory (12) rsync error: error in IPC code (code 14) at main.c(552) Here is part of the log: 2005/12/04 03:35:54 [4345] rsync on Prod/ from mirror.company.com (10.0.0.16) 2005/12/04 03:56:52 [4337] sent 17599277 bytes received 467 bytes total size 144263481292 2005/12/04 23:06:55 [4345] rsync: connection unexpectedly closed (465 bytes received so far) [sender] 2005/12/04 23:06:55 [4345] rsync error: error in rsync protocol data stream (code 12) at io.c(434) 2005/12/04 23:06:55 [4345] rsync: writefd_unbuffered failed to write 76 bytes: phase "unknown" [sender]: Broken pipe (32) 2005/12/04 23:06:55 [4345] rsync error: error in rsync protocol data stream (code 12) at io.c(1099) I'm using rsync version 2.6.5 protocol version 29. The same script runs for other modules but rsync always seems to fail/crash for one particular module. Please note that everything was running file before, even for this module. All the module parameters are identical. I suspect the reason being the very large number of files in that module. Can anyone help me find the cause of the problem and hopefully the solution? -------------- next part -------------- HTML attachment scrubbed and removed
On Mon, Dec 05, 2005 at 09:57:39AM +0400, apache7@gmx.net wrote:> rsync: fork failed in do_recv: Cannot allocate memory (12)That is an OS error: the fork() system call failed with ENOMEM, which typically means that you don't have enough swap space available for the new process. Adding more swap should fix this. Alternately, dividing up the failing rsync command into multiple hierarchies should also avoid the problem, because rsync will not grow to use so much memory. ..wayne..
Reasonably Related Threads
- rsync hang, more details [LONG]
- DO NOT REPLY [Bug 5701] New: deadlock on local rsyncing, bisected to commit f303b749f2843433c9acd8218a4b9096d0d1bb8d
- PATCH/RFC: Another stab at the Cygwin hang problem
- error in IPC Code (code 14) at main.c(669) [receiver=2.6.9cvs]
- "fork failed in do_recv: Not enough space"