On Wed, Apr 09, 2014 at 02:33:51AM -0400, Mike Paul wrote:
> I ran into this bug today while copying a tree of files from one Debian
> amd64 system to another, both running sid and with the rsync package
> version 3.1.0-2 installed. The options used were "-avzh", plus
> "--progress" and some "--exclude" options that I doubt are relevant.
>
> The first file that failed was 1078591488 bytes in size, and it failed
> with the message:
>
> inflate returned -3 (6 bytes)
> rsync error: error in rsync protocol data stream (code 12) at token.c(557)
> [receiver=3.1.0]
> rsync: [generator] write error: Broken pipe (32)
> rsync error: error in socket IO (code 10) at io.c(837) [generator=3.1.0]
Just another data point.
I have an rsync server with Debian stable, running "rsync version 3.0.7
protocol version 30".
I used to be able to sync to it from another machine running Debian
testing, but today after upgrading to "rsync version 3.1.0 protocol
version 31", I ran into this bug.
The server (running in rsync --daemon mode) complained:
inflate returned -3 (0 bytes)
rsync error: error in rsync protocol data stream (code 12) at token.c(546)
[receiver=3.0.7]
rsync: connection unexpectedly closed (114 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[generator=3.0.7]
Trying from that same client without --compress worked just fine,
similar to what others have said in this bug.
The same command, from an Ubuntu 13.10 with "rsync version 3.0.9
protocol version 30", always worked just fine.
I hope this helps!
Thanks,
Alberto
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
