On Fri, 2009-11-27 at 15:00 -0500, Matt McCutchen wrote: > On Fri, 2009-11-27 at 10:56 -0800, Wayne Davison wrote: > > On Fri, Nov 27, 2009 at 7:45 AM, Dieter Stüken <[email protected]> > > 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. [...] > > Wayne, > > Would you please consider adding this to the FAQ? This is the sort of > inscrutable error whose explanation I'm never going to remember.
Here is the FAQ patch. -- Matt
diff --git a/FAQ.html b/FAQ.html index cd504d8..9220e42 100644 --- a/FAQ.html +++ b/FAQ.html @@ -20,6 +20,7 @@ <li><a href="#9">spaces in filenames</a><br> <li><a href="#10">ignore "vanished files" warning</a><br> <li><a href="#11">read-only file system</a><br> +<li><a href="#12">multiplexing overflow 101:7104843</a><br> </ul></td></tr></table> <hr> @@ -260,6 +261,16 @@ exit $e</pre></blockquote> daemon then you probably forgot to set "read only = no" for that module. <hr> +<h3><a name=12>multiplexing overflow 101:7104843</a></h3> + +<p>This mysterious error, or the similar "invalid message 101:7104843", can +happen if one of the rsync processes is killed for some reason and a message +beginning with the four characters "Kill" gets inserted into the protocol +stream as a result. To solve the problem, you'll need to figure out why rsync +is being killed. +See <a href="https://bugzilla.samba.org/show_bug.cgi?id=5727";>this bug report</a>. + +<hr>
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
