rsync error: protocol incompatibility (code 2) at main.c(451)

[Tony at ServaCorp.com]

Dunno if this has any relationship (or even if this is the right place to
break in)

SERVER: rsync-HEAD-20050314-2227GMT
rsync error: protocol incompatibility (code 2) at io.c(915)
rsync error: protocol incompatibility (code 2) at sender.c(157)

CLIENT: rsync  version 2.6.3  protocol version 29

Server upgraded from VERY OLD 2.4.1-2 (rpm) to latest (bugs&all)
Server to current version 2.6.3 and everything is fine, as far as I am
concerned.

I have the latest on a very sacrificial clone of the SERVER and can
duplicate the errors.

Mar 15 10:21:46 2bizbox rsyncd[24957]: rsyncd version 2.6.4pre2 starting,
listening on port 873
Mar 15 10:21:46 2bizbox modprobe: modprobe: Can't locate module net-pf-10

Mar 15 10:50:52 2bizbox rsyncd[1204]: rsyncd version 2.6.3 starting,
listening on port 873
Mar 15 10:50:52 2bizbox modprobe: modprobe: Can't locate module net-pf-10

The above is from the server.
The clone is sufficiently messed up that most everything is disabled.
Better to make mistakes where the consequences are irrelevant.
If this is relevant or if I can help with it, please let me know.
I've been around awhile, but it's safer to assume that I'm a very green
newbie.

(You guys are too fast)
CLONE:  rsync-HEAD-20050315-1733GMT]
[root at wf1 local]# rsync -avPLz --password-file=/etc/rsync/rsync.2bb
rsync-2bb at 172.30.0.13::mysql-2bb/srv/b* /tmp/
receiving file list ...
6 files to consider
bm.MYD
Invalid file index: 65536 (count=6) [sender]
rsync error: protocol incompatibility (code 2) at sender.c(157)
rsync: connection unexpectedly closed (139 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(363)
rsync: connection unexpectedly closed (123 bytes received so far)
[generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(363)

Different place in io.c  (but different test from different server)
Same result going back to rsync-HEAD-20050314-2227GMT on clone.
Actually I'm impressed. I like things that do little to no damage when
broken.


-----Original Message-----
From: rsync-bounces+tony=servacorp.com at lists.samba.org
[mailto:rsync-bounces+tony=servacorp.com at lists.samba.org]On Behalf Of
Wayne Davison
Sent: Tuesday, March 15, 2005 11:37 AM
To: Dag Wieers
Cc: rsync at lists.samba.org
Subject: Re: rsync error: protocol incompatibility (code 2) at
main.c(451)


On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote:
> 	Invalid packet at end of run [sender]

OK, this was a combination of --delay-updates and --hard-links that was
causing a problem at the end of the run.  I've checked in a fix to CVS,
and the latest "nightly" tar file has this fix present.  I'm confident
that will take care of the problem for you.  Thanks for the help!

..wayne..
--
To unsubscribe or change options:
https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html