inflate returned -3 - resolved?

[Dave Dykstra]

Can you try 2.5.5 on the client side too?  I don't think there were
zlib-related changes in 2.5.5, but it is worth a try.  There have been
problems in recent versions with the -z option but I don't recognize that
particular one.  Can you make a file publicly available that can
consistently cause the problem so other people can reproduce it?

- Dave Dykstra

On Fri, Jul 26, 2002 at 01:03:18PM -0400, William Stearns wrote:
> Good day, all,
> 	Sorry for yet _another_ slef-reply, but removing "-z" from the 
> command line appears to fix the problem.
> 	Is this worth investigating any further?
> 	Cheers,
> 	- Bill
> 
> On Fri, 26 Jul 2002, William Stearns wrote:
> 
> > On Fri, 26 Jul 2002, William Stearns wrote:
> > 
> > > 	I'm trying to transfer a 174M file to a system with 1.2G free.  
> > > Other files in the tree come over just fine, but this transfer dies 
> > > partway through:
> > > 
> > > rsync -avvz -e ssh --partial --progress server.with.the.file:/server/directory /local/directory
> > > 
> > > opening connection using ssh server.with.the.file rsync --server --sender -vvlogDtprz --partial . /local/directory 
> > > receiving file list ... 
> > > 30 files to consider
> > > OneFile is uptodate
> > > ...
> > > path/to/hosts.tar.bz2
> > > inflate returned -3 (0 bytes)    0:02:17
> > > rsync error: error in rsync protocol data stream (code 12) at token.c(416)
> > > rsync: connection unexpectedly closed (792 bytes read so far)
> > > rsync error: error in rsync protocol data stream (code 12) at io.c(151)
> > > 
> > > 	Client is using rsync 2.5.4 from RH7.3
> > > 
> > > 	Server is using rsync 2.4.6 from rh6.2 (sorry about the old 
> > > version; this machine is one we're not supposed to ugrade; long story).
> > > 
> > > 	File to be transferred:
> > > -rw-r--r--    1 wstearns wstearns 174555493 Dec  6  2000 hosts.tar.bz2
> > > 
> > > 	Adding two more -v's makes the negotiation more verbose, but the 
> > > error still shows up:
> > > 
> > > chunk[1796] of size 16384 at 29425664 offset=29425664
> > > chunk[1797] of size 16384 at 29442048 offset=29442048
> > > chunk[1798] of size 16384 at 29458432 offset=29458432
> > > chunk[1799] of size 16384 at 29474816 offset=29474816
> > > chunk[1800] of size 16384 at 29491200 offset=29491200
> > > chunk[1801] of size 16384 at 29507584 offset=29507584
> > > inflate returned -3 (0 bytes)
> > > rsync error: error in rsync protocol data stream (code 12) at token.c(416)
> > > rsync: connection unexpectedly closed (792 bytes read so far)
> > > rsync error: error in rsync protocol data stream (code 12) at io.c(151)
> > > 
> > > 	I would sincerely like to help debug this; any suggestions of what 
> > > to inspect?  I'll try to get the server version up to 2.5.5 in the hopes 
> > > that might help.
> > 
> > 	Bringing the server up to 2.5.5 did not change the error message:
> > inflate returned -3 (0 bytes)    0:01:36
> > rsync error: error in rsync protocol data stream (code 12) at token.c(416)
> > rsync: connection unexpectedly closed (792 bytes read so far)
> > rsync error: error in rsync protocol data stream (code 12) at io.c(151)
> > 
> > 	/me scratches head.
> 
> ---------------------------------------------------------------------------
> 	"Give a man a fish and you feed him for a day; give him a
> freshly-charged electric eel and chances are he won't bother you for
> anything ever again."
> (Courtesy of Thomas Harris <spiny_norman at piranhabrothers.org>)
> --------------------------------------------------------------------------
> William Stearns (wstearns at pobox.com).  Mason, Buildkernel, named2hosts, 
> and ipfwadm2ipchains are at:                        http://www.stearns.org
> --------------------------------------------------------------------------
> 
> 
> 
> -- 
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html