I've been getting this error message for a few days from a customer's server and we can't seem to decipher it. I googled for it and only found references to it with respect to much older versions of rsync. We're running the Debian packaged version of rsync version 2.6.2-3. The customer side is running 2.6.3 compiled from source. #### inflate (token) returned -5 rsync error: error in rsync protocol data stream (code 12) at token.c(487) rsync: connection unexpectedly closed (31461294 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(343) Command exited with non-zero status 12 #### Timing information on the run: real 875.26 user 45.04 sys 66.38 Exact (redacted) commandline used: /usr/bin/time -p /usr/bin/rsync -e /usr/bin/ssh --archive --compress --sparse --stats --delete --numeric-ids --partial --exclude "/dev" --exclude "/proc" --exclude "/sys" --exclude "/mnt" remote.server.org:/ /local/destination/path Does anyone have any insights? -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
On Mon, Dec 06, 2004 at 09:38:14AM -0800, Chuck Wolber wrote:> inflate (token) returned -5You should be able to avoid this error by turning off the --compress option. To figure out why it is occurring would require someone to debug a failure case. If you can narrow it down to a particular set of files that always causes the error and make them available, it would allow some debugging to occur. I haven't seen any compression failures in recent versions, so I can't debug it without seeing a failure. ..wayne..