Hello, Server rsyncd [root@data1 steve]# rsync --version rsync version 2.6.9 protocol version 29 [root@data1 steve]# uname -a Linux data1.contact-24-7.local 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 26 14:30:58 EDT 2007 i686 i686 i386 GNU/Linux [root@data1 steve]# Client rsync [root@srv01 cron.daily]# rsync --version rsync version 2.6.9 protocol version 29 [root@srv01 cron.daily]# uname -a Linux srv01.wcsl.local 2.6.9-42.0.10.EL #1 Tue Feb 27 09:24:42 EST 2007 i686 i686 i386 GNU/Linux [root@srv01 cron.daily]# Error received when trying to use rsync -vz on the client inflate (token) returned -5 rsync error: error in rsync protocol data stream (code 12) at token.c(458) rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown" [generator]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(909) Seems to work fine without compression -z flag omitted. Thanks in advance Regards /Steve
On 7/19/07, WCSL <rsync@wcsl.net> wrote:> Error received when trying to use rsync -vz on the client > > inflate (token) returned -5 > rsync error: error in rsync protocol data stream (code 12) at token.c(458) > rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown" > [generator]: Broken pipe (32) > rsync error: error in rsync protocol data stream (code 12) at io.c(909) > > Seems to work fine without compression -z flag omitted.There have been occasional reports of -z getting corrupted in the past, but we've never gotten a reproducible case to investigate and find the underlying problem. If you run the command repeatedly, does that same error occur every time? Even better if it still happens with the same files on a different pair of machines. If so, please send the source and destination files prior to the run to Wayne Davison <wayned@samba.org>, the rsync maintainer, unless they're big and/or private in which case you should discuss other arrangements with him. Matt
On Thu, 19 Jul 2007, WCSL wrote:> Seems to work fine without compression -z flag omitted.Is this going through a Watchguard firewall at any point? ..Chuck.. -- http://www.quantumlinux.com Quantum Linux Laboratories, LLC. ACCELERATING Business with Open Technology "The measure of the restoration lies in the extent to which we apply social values more noble than mere monetary profit." - FDR 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
On 8/14/2010 3:09 AM, Matt McCutchen wrote:> On Fri, 2010-08-13 at 11:26 -0400, Brian K. White wrote: >> I have sample data that exposes this repeatably: >> http://lists.samba.org/archive/rsync/2008-October/021889.html > > Thanks, but we figured out the problem several months ago and it should > be fixed in rsync 3.0.7: > > https://lists.samba.org/archive/rsync/2009-December/024441.html >Ahh great... Confirmed. I had a mix of 3.0.6 and 3.0.7 machines 32 and 64bit, but I guess in all that I never did a 3.0.7<->3.0.7 test just to be sure. My test data does not fail when both sides of the connection are 3.0.7 Sorry for the noise. -- bkw