Re: multiplexing overflow errors
On Fri, Dec 4, 2009 at 11:26 PM, Matt McCutchen m...@mattmccutchen.netwrote: Here is the FAQ patch. Thanks! I've updated the FAQ. ..wayne.. -- 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
Re: multiplexing overflow errors
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 d.stue...@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. [...] 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 @@ lia href=#9spaces in filenames/abr lia href=#10ignore vanished files warning/abr lia href=#11read-only file system/abr +lia href=#12multiplexing overflow 101:7104843/abr /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 +h3a name=12multiplexing overflow 101:7104843/a/h3 + +pThis 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
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 -- 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
Re: multiplexing overflow errors
On Fri, Nov 27, 2009 at 7:45 AM, Dieter Stüken d.stue...@conterra.dewrote: 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.. -- 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
Re: multiplexing overflow errors
On Fri, 2009-11-27 at 10:56 -0800, Wayne Davison wrote: On Fri, Nov 27, 2009 at 7:45 AM, Dieter Stüken d.stue...@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. [...] 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. -- Matt -- 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
multiplexing overflow
On Fri, Mar 17, 2006 at 07:16:19PM +0300, ? ??? wrote: / multiplexing overflow 101:7104843 [receiver] / This indicates that the protocol got corrupted somehow because that is saying that the receiver got a MSG_DELETED message with a 7104843-byte buffer attached (which rsync is telling you is too big), but you're not even deleting files. What version of rsync are you using? == == Hi Wayne, i encountered this one as well with a rsync 2.6.4 and 2.6.6 pair. In my case i got it because a run-a-way script produced a very deep folder structure with a small file in all these folders, like: /local/transfer/heleen/tmp.1526964/tmp.1526964/tmp.1526964/tmp.1526964/...(very_deep).../tmp.1526964/tmp.1526964/MR16511 hope this helps vincent -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: multiplexing overflow
On Thu, Dec 28, 2006 at 02:22:01PM +0100, Vincent Kersten wrote: i encountered this one as well with a rsync 2.6.4 and 2.6.6 pair. In my case i got it because a run-a-way script produced a very deep folder structure with a small file in all these folders, like: In which case it's a valid error -- the filename overflowed the buffer (the prior error was only a protocol corruption due to the impossible hugeness of the message length it mentioned). Newer rsync versions have more headroom in the message buffers, so upgrading the 2.6.4 version may allow the transfer to complete without error (but it may not be enough if the dirs are way too deep). ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Multiplexing overflow
On Wed, Mar 22, 2006 at 08:08:28PM +0300, ?? ?? wrote: I'm using rsync v.2.6.6 (with protocol version 29). Is this the same on both ends of the connection? If the version of rsync on the sending side is older than 2.6.4, I know of one protocol- corrupting bug that might be causing this. If it's 2.6.4 or newer, then it's either an unknown rsync bug or a bug in the data being transported inaccurately by the remote shell or networking code. There is one way figure out which of these two areas is the actual cause: There is a program in the support dir named savetransfer.c. If you build that program by typing make inside the support dir, you can copy the resulting binary onto both ends of the connection and run it like this: /usr/local/bin/rsync -avze /tmp/savetransfer -o /tmp/from.server ssh --rsync-path=/tmp/savetransfer -o /tmp/to.client rsync [EMAIL PROTECTED]:remote_path local_path This makes a copy of the data that the server is sending back to the client (receiver), and a copy of what the client actually received. The two resulting files should be identical (or at least only differ by the to.client file being slightly more truncated than the from.server file). If there is a data difference, then you have a problem with the sending of the bytes that is outside the control of rsync. If the bytes are the same, you might want to contact me off the list if you'd be willing to let me see the to.client data, or at least some portion of it from near the end. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Multiplexing overflow
On Fri, Mar 17, 2006 at 07:16:19PM +0300, ? ??? wrote: multiplexing overflow 101:7104843 [receiver] This indicates that the protocol got corrupted somehow because that is saying that the receiver got a MSG_DELETED message with a 7104843-byte buffer attached (which rsync is telling you is too big), but you're not even deleting files. What version of rsync are you using? ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Multiplexing overflow
I'm using rsync v.2.6.6 (with protocol version 29). Wayne Davison wrote: On Fri, Mar 17, 2006 at 07:16:19PM +0300, ? ??? wrote: multiplexing overflow 101:7104843 [receiver] This indicates that the protocol got corrupted somehow because that is saying that the receiver got a MSG_DELETED message with a 7104843-byte buffer attached (which rsync is telling you is too big), but you're not even deleting files. What version of rsync are you using? ...wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Multiplexing overflow
Hi, List! I have a problem with rsync. I was trying to synchronize directory trees on 2 servers and got following error: multiplexing overflow 101:7104843 [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(809) Complete rsync's output: /usr/local/bin/rsync -avzp [EMAIL PROTECTED]:remote_path local_path receiving file list ... done ./ DelphiStudio7.rar readme.koi8.txt readme.txt .ssh/ backup/ ssl/ ssl/data/ ssl/htdocs/ www/ www/data/ www/htdocs/ www/htdocs/.htaccess www/htdocs/DelphiStudio7.rar multiplexing overflow 101:7104843 [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(809) What does this mean? I've googled error message but couldn't find anything relevant. Any help will be greatly appreciated! Thanks in advance -- Regards, Eugene Kosov. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
