rsync - Nov 2009 - multiplexing overflow errors

I'm using rsync 3.0.6 between two solaris 8/10 hosts an I frequently get
"multiplexing overflow" errors:

log/20091123_223901/dresden.log:multiplexing overflow 101:7104843 [sender]
log/20091123_223901/frankfurt.log:multiplexing overflow 101:7104843 [sender]
log/20091123_223901/hannover.log:multiplexing overflow 101:7104843 [sender]
log/20091123_223901/muenchen.log:multiplexing overflow 101:7104843 [sender]
log/20091123_223901/stuttgart.log:multiplexing overflow 101:7104843 [sender]
log/20091124_193051/dresden.log:multiplexing overflow 101:7104843 [sender]
log/20091124_193051/muenchen.log:multiplexing overflow 101:7104843 [sender]

I have to admit that I have to syncronize HUGE directories with up to 1 000 000
tiny files!
But this does not fail in general. After a few retries it works, but it is
annoying.

Any clue?
I compiled the source myself, so I may be able to debug it or to include some
diagnostic messages to narrow the problem.

My current version is:

rsync  version 3.0.6  protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, no IPv6, batchfiles, inplace,
    append, ACLs, no xattrs, iconv, no symtimes

rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
are welcome to redistribute it under certain conditions.  See the GNU
General Public Licence for details.

Dieter

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20091127/022c23c6/attachment.html>

On Fri, Nov 27, 2009 at 7:45 AM, Dieter St?ken <D.Stueken at
conterra.de>wrote:
>  log/20091123_223901/dresden.log:multiplexing overflow 101:7104843
> [sender]
>
This has come up before.  That number translates into the byte sequence 0x4b
0x69 0x6c 0x6c, which is "Kill" in ASCII.  So, something is outputting
a
"Killed ..." message to stdout instead of the proper stderr (which you
may
want to report to the Solaris folks so they can fix it).  To fix the
rsync-copy failures, you should figure out why rsync is being killed.
Perhaps your system logs will tell you.  Or maybe attaching a
syscall-tracing utility to the appropriate process would reveal the whole
message.

..wayne..
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20091127/69044375/attachment.html>