I am wondering if there are known incompatibilities
between 2.6.3 and 2.6.4?
I have a debian box with 2.6.4 and a FC3 box with
2.6.3. Most of the time rsync works fine between the
two but I am running this command on FC3 box:
rsync -azvv --stats --delete
--files-from=/root/.rsb2.tmp /
nathan@debian:/home/backup/bkp.01
And I am getting this error message:
building file list ...
[sender] expand file_list to 131072 bytes, did move
rsync: writefd_unbuffered failed to write 4092 bytes:
phase "send_file_entry" [sender]: Broken pipe (32)
delta-transmission enabled
Invalid file index: 268456790 (count=0) [receiver]
rsync error: protocol incompatibility (code 2) at
sender.c(156)
rsync: connection unexpectedly closed (8513 bytes
received so far) [generator]
rsync error: error in rsync protocol data stream (code
12) at io.c(420)
rsync: connection unexpectedly closed (8 bytes
received so far) [sender]
rsync error: error in rsync protocol data stream (code
12) at io.c(359)
If I don't use the files-from option things seem to
work just fine. Also if I change nathan@debian to
nathan@fedora (so that it is just rsyncing locally) it
works fine.
Any Ideas?
Which box needs upgrading?
Or do they both need to be upgraded to 2.6.5?
Nathan Bullock
PS. I just want to say thanks to all those who gave
answers to my last post ("Two Questions"). They were
very helpful.
Visit my website at http://www.nathanbullock.org
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
On Sun, Jun 26, 2005 at 01:02:42PM -0400, Nathan Bullock wrote:> Invalid file index: 268456790 (count=0) [receiver]This is the pertinent error from that sequence -- this means that the data being sent over the socket has either been corrupted, or out-of- sync somehow. The first thing to check is to see if the file compression is causing the problem by turning off the -z option. If that fixes things, upgrading to 2.6.5 (or 2.6.4, but 2.6.5 is better) on the sending machine will fix it. If that doesn't work, you look in the the support dir of rsync for the C source named savetransfer.c, you can use it to diagnose the problem: You can build it using "make" in the support dir and then put a copy on both machines e.g. in the /tmp dir. Since you are pushing files, the comments in savetransfer.c explain that this invocation will capture the data being sent to the receiver: rsync -av --rsh="/tmp/savetransfer -i /tmp/from.sender ssh" \ --rsync-path="/tmp/savetransfer -i /tmp/to.receiver rsync" FILES HOST:DEST (Tweak that with your own options.) Also read the comments about the limits of the savetransfer program in its default implementation. If the transfer fails (with the same error -- not a timeout) and the two files differ, your connection is not sending the data correctly; if the files are the same, let me know and I can help you diagnose the problem. ..wayne..