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. Thanks for your time anand
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: jw@pegasys.ws Remember Cernan and Schmitt
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:jw@pegasys.ws] Sent: Tuesday, August 26, 2003 1:07 PM To: rsync@lists.samba.org 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: jw@pegasys.ws 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
Thanks jw Your suggestion of removing -e from the rsync options seems to have fixed the problem. We have been able to synchornize large number of files between the 3 environments with no weird protocol incompatibilities or freezes.. Do you think it is better idea use ssh instead of rsh to overcome the blocking/non-blocking io incompatibility. The environments are internal environments not visible to the outside world and hence could do without ssh Thanks for your time cheers anand -----Original Message----- From: jw schultz [mailto:jw@pegasys.ws] Sent: Tuesday, August 26, 2003 2:02 PM To: rsync@lists.samba.org Subject: Re: Rsync hangs with protocol incompatibility issues On Tue, Aug 26, 2003 at 01:34:21PM +0530, Anand Raman wrote:> 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 theA little madness helps in this business. But the frustration of such inconsistant behavior can lead to anger.> 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 helpsThe fact that the error messages vary like this indicates some serious communications problems. You mention it seems to get stuck. That could be an issue with blocking vs. non-blocking io. There is some odd internal logic involved with selecting the blocking or non-blocking having to do with the value of the -e option. I think rsh wants blocking-io but using the -e option turns that off if the -e value is not exactly the same as the build-time default value because most other remote shells want non-blocking. You might try either adding --blocking-io or changing your commandline to specify the user name as part of the remote system ala "araman@bpearth:blahblah" instead of using the -e option. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html