Re(2): rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)

Rönnblom Janåke /Teknous jan-ake.ronnblom at skeria.skelleftea.se
Wed Feb 13 05:00:10 EST 2002


dwd at bell-labs.com skriver:
>Ah, 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

Yes, it dies after the same time all the times. A crashrun takes about
20 minutes.
>
>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

Trying without -v now and no difference.
>
>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.
>
Checked the unixbox and the process is using about 50M (according to top)
before crashing
and the machine has 256MB and does nothing besides being subject to my
rsync testing.

However I did another test with 2.5.3pre and this is what i got on the
client:

rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)

and on the server:

select(4, [3], NULL, NULL, {10800, 0})  = 1 (in [3], left {10800, 0})
read(3, "TEM.DAT", 7)                   = 7
time(NULL)                              = 1013540288
select(4, [3], NULL, NULL, {10800, 0})  = 1 (in [3], left {10800, 0})
read(3, "\377\377\377\377", 4)          = 4
time(NULL)                              = 1013540288
select(4, [3], NULL, NULL, {10800, 0})  = 1 (in [3], left {10800, 0})
read(3, "\374\2004:>\34\5P", 8)         = 8
time(NULL)                              = 1013540288
select(4, [3], NULL, NULL, {10800, 0})  = 1 (in [3], left {10800, 0})
read(3, ".BAK", 4)                      = 4
time(NULL)                              = 1013540288
select(4, [3], NULL, NULL, {10800, 0})  = 1 (in [3], left {10800, 0})
read(3, "m", 1)                         = 1
time(NULL)                              = 1013540288
select(4, [3], NULL, NULL, {10800, 0})  = 1 (in [3], left {10800, 0})
read(3, "\3", 1)                        = 1
time(NULL)                              = 1013540288
select(4, [3], NULL, NULL, {10800, 0})  = 1 (in [3], left {10800, 0})
read(3, "\0\0\262\313", 4)              = 4
time(NULL)                              = 1013540288
select(4, NULL, [3], NULL, {10800, 0})  = 1 (out [3], left {10800, 0})
write(3, "R\0\0\10overflow: flags=0x6d l1=3 l2"..., 86) = 86
time(NULL)                              = 1013540288
select(4, NULL, [3], NULL, {10800, 0})  = 1 (out [3], left {10800, 0})
write(3, "-\0\0\10ERROR: buffer overflow in re"..., 49) = 49
time(NULL)                              = 1013540288
rt_sigaction(SIGUSR1, {SIG_IGN}, {0x8050ed4, [], SA_RESTART|0x4000000}, 8)
= 0
rt_sigaction(SIGUSR2, {SIG_IGN}, {0x8050ef4, [], SA_RESTART|0x4000000}, 8)
= 0
select(4, NULL, [3], NULL, {10800, 0})  = 1 (out [3], left {10800, 0})
write(3, "K\0\0\10rsync error: error allocatin"..., 79) = 79
time(NULL)                              = 1013540288
munmap(0x2aabf000, 4096)                = 0
_exit(22)                               = ?

I have a error above about "error allocatin" memory and "TEM.DAT" was in
the
old trace also (2.4.6) but top and ps afux said it used 50MB...

Nothing in the other logfiles.

How can I trace this error further?

=====================================================
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
-----------------------------------------------------






More information about the rsync mailing list