Rönnblom Janåke /Teknous
2002-Feb-12 23:18 UTC
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
Trying to rsync between win2k machines. rsync version is 2.5.3pre (downloaded today) This is the message after 368100 files have been checked: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) My cmdline is : c:\sbin\rsync\rsync -az /cygdrive/d/Home xxx@xxx.skelleftea.se::dropZone/GY/ba-disk01 --stats -v -P --timeout=84600 I have tried with both with and without -z (-az or -a) On the server im using cygwinsrv with the following parameters to rsync --config=/etc/rsyncd.conf --daemon --no-detach ====================================================Jan?ke R?nnblom SKERIA Utveckling AB (Teknous) Assistentgatan 23 931 77 Skelleftea (Sweden) ----------------------------------------------------- Phone : +46-910-585424 Mobile : 070-3970743 Fax : +46-910-585499 URL : http://skeria.skelleftea.se -----------------------------------------------------
Dave Dykstra
2002-Feb-13 03:40 UTC
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
On Tue, Feb 12, 2002 at 01:18:49PM +0100, R?nnblom Jan?ke /Teknous wrote:> > Trying to rsync between win2k machines. > > rsync version is 2.5.3pre (downloaded today) > > This is the message after 368100 files have been checked: > rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) > > My cmdline is : > > c:\sbin\rsync\rsync -az /cygdrive/d/Home > xxx@xxx.skelleftea.se::dropZone/GY/ba-disk01 --stats -v -P --timeout=84600 > > I have tried with both with and without -z (-az or -a) > > On the server im using cygwinsrv with the following parameters to rsync > > --config=/etc/rsyncd.conf --daemon --no-detachAh, I see you posted more details for the same problem. That message comes when one process on the receiver side interrupts the other because it is is about to die, and doesn't really say anything about what the real problem might be. I assume it's dying before 84600 seconds, right? Have you ever tried it without -v? That's been known to cause problems before, although I'm not sure if they've been fixed. Be sure to check to see if the log file on the server side has anything useful. Have you ever tried pulling the files from a server rather than pushing to it? The rsync server mode was never really intended for significant writing, more for reading, and it has some quirks when used for writing (not to say that dying completely is just a "quirk"). Again, it's possible you're running out of memory with that many files. - Dave Dykstra
Reasonably Related Threads
- MS-DOS, WinXP SP2 with 3.05 and 3.0.6rc2
- rsync 2.4.6-3 cygwin : transfer interrupted (code 22) at util.c(211)
- winbind trouble under load?
- rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
- [Bug 2760] some time rsync is exiting with received SIGUSR1 or SIGINT (code 20) at rsync.c(229).