Bug 3334 - some time rsync is exiting with received SIGUSR1 or SIGINT (code 20) at rsync.c(229).
Summary: some time rsync is exiting with received SIGUSR1 or SIGINT (code 20) at rsync...
Status: RESOLVED WORKSFORME
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 2.6.6
Hardware: All Linux
: P3 major (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-15 08:53 UTC by Bill Kuykendall
Modified: 2005-12-15 17:12 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bill Kuykendall 2005-12-15 08:53:59 UTC 
+++ This bug was initially created as a clone of Bug #2760 +++

Rsync dies consistently after quite some time.  My filelist is huge.
Here's the error with 2.6.6 on SLES9 x86_64:
received SIGUSR1 or SIGINT (code 20) at rsync.c(163) 

The las guy was using version 2.5.7:
We are running the rsync over the Network, and it is getting killed some 
times. The error is as below.

received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
Comment 1 Wayne Davison 2005-12-15 17:12:53 UTC 
I noticed recently that this message is inaccurate:  it also gets output if rsync gets killed by a SIGTERM or SIGHUP.  I'd imagine that your OS is killing rsync because it is consuming too much memory (check your system logs to know for sure).  I'd suggest dividing the file list up into multiple hierarchies and trying again.