Hi jw Thanks for responding..
1) At work we end up using outlook. That could possibly explain a bit about formatting 2) The error message varies from invocation to invocation. Sometimes it exists with a error message and sometimes it seems to be stuck doing something. (You can think I am mad but that's the way I am seeing the problem). To further isolate the problem I am trying to sync the jboss code repository and this is what I see on 2 consecutive runs $ /usr/local/bin/rsync -aP --stats -e 'rsh -l araman' --rsync-path=/usr/local/bin/rsync jboss-3.2.2RC2-src bpearth:/export/spare/home/araman unexpected tag -7 rsync error: error in rsync protocol data stream (code 12) at io.c(315) On the second run the error message which gets printed is unexpected tag 105 rsync error: error in rsync protocol data stream (code 12) at io.c(315) 3) This happens after approximately 2110 of 5500 files have been transferred to the remote machine. This number ofcourse varies from run to run. But I consistently get to t see a error message. 4) The exact text of the error message varies. Let me know if I could be of any more help Hope this helps anand -----Original Message----- From: jw schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 26, 2003 1:07 PM To: [EMAIL PROTECTED] Subject: Re: Rsync hangs with protocol incompatibility issues On Tue, Aug 26, 2003 at 12:53:27PM +0530, Anand Raman wrote: If you are using Solaris, why was your email formatted so poorly? > hi guys > > Environment 2 servers (SunOS 5.8) rsync 2.5.6 > > Problem For a disaster recovery solution, we are running trying to > synchornize interwoven backup stores between these 2 environments > (server A and server B) > > The rsync operation is initiated over the network using 'rsh'. Once > initiated from server A the rsync operation freezes with no > indication. When the debug flag is enabled we get to see the following > error message > > rsync error: protocol incompatibility (code 2) at > sender.c(135) > > Both servers have the same rsync version (2.5.6 protocol version 26). > It is also interesting to note is that we are able to synchronize > files from server B onto server A. > > Can anyone suggest pointers on how we could debug this problem. > > I could provide you with more pointers if you let me know where to > find them. Immediately above that you should have the real error message, "Invalid file index %d (count=%d)". It might help to know what those numbers are as well as any preceding error messages. From the almost nothing you have provided this looks like a communications problem. PS. Why do people send only the last error message instead of the the first when it is the first that starts the cascade effect? -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
