UNCLASSIFIED//// I am seeing the following errors occasionally when doing an rsync between servers (Solaris 9) at the local and remote site. Has anyone seen these errors before or know what they are? rsync error: error in rsync protocol data stream (code 12) at io.c(1122) [sender=2.6.9] rsync error: protocol incompatibility (code 2) at io.c(954) [sender=2.6.9] rsync error: protocol incompatibility (code 2) at io.c(960) [sender=2.6.9] rsync error: protocol incompatibility (code 2) at sender.c(174) [sender=2.6.9] rsync error: protocol incompatibility (code 2) at io.c(954) [sender=2.6.9] rsync error: protocol incompatibility (code 2) at io.c(960) [sender=2.6.9] rsync error: protocol incompatibility (code 2) at sender.c(174) [sender=2.6.9] Both servers are using 2.6.9 The only changes that I can think of that have been made is the amount of data is continuously growing. We have had the networking group take a look at their switches and routers bc we see "Broken Pipe" errors soon after we get one of the above errors, but they are not seeing anything on their end. Does anyone have any ideas? Thanks Theresa Peter Unix Team CSI - Data Services ISA-USAAC Theresa.Peter@usaac.army.mil (502) 626-0649 UNCLASSIFIED//// -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4995 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20070904/077a4498/smime.bin
On 9/4/07, Peter, Theresa M Ms CONT USAAC <THERESA.PETER@usaac.army.mil> wrote:> I am seeing the following errors occasionally when doing an rsync between > servers (Solaris 9) at the local and remote site. Has anyone seen these > errors before or know what they are? > > rsync error: error in rsync protocol data stream (code 12) at io.c(1122) > [sender=2.6.9] > rsync error: protocol incompatibility (code 2) at io.c(954) [sender=2.6.9] > rsync error: protocol incompatibility (code 2) at io.c(960) [sender=2.6.9] > rsync error: protocol incompatibility (code 2) at sender.c(174) > [sender=2.6.9] > rsync error: protocol incompatibility (code 2) at io.c(954) [sender=2.6.9] > rsync error: protocol incompatibility (code 2) at io.c(960) [sender=2.6.9] > rsync error: protocol incompatibility (code 2) at sender.c(174) > [sender=2.6.9] > > Both servers are using 2.6.9> We have had the networking group take a look at their switches and routers > bc we see "Broken Pipe" errors soon after we get one of the above errors, > but they are not seeing anything on their end.The "Broken Pipe" and the "error in rsync protocol data stream" are both aftermath of a previously occurring error. The other errors all mean that the sender received something invalid from the generator. That could indicate either a bug in rsync or corruption in the network connection. You could dump the data that each side sends and receives over the network using the "savetransfer" program that comes in support/ of the rsync source package ( http://rsync.samba.org/ftp/rsync/rsync-2.6.9.tar.gz ) to determine whether network corruption is occurring. Matt
UNCLASSIFIED//// I am still trying to figure out whether or not we have that savetransfer option already on the box. It may take me a bit to get a new package installed due to software cycle that we have to go through before putting it on the box. Looking into this more... The following errors were the first that we saw: rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1122) [sender=2.6.9] rsync: read errors mapping "/soinc/soinc_std_001" (in CYA): No data available (61) rsync error: some files could not be transferred (code 23) at main.c(683) [sender=2.6.9] Since then we have been seeing the following errors on every rsync: Invalid checksum length 39976960 [sender] **** Variable lengths listed **** rsync error: protocol incompatibility (code 2) at io.c(954) [sender=2.6.9] Invalid remainder length 39976960 [sender] rsync error: protocol incompatibility (code 2) at io.c(960) [sender=2.6.9] Invalid file index: 2046101527 (count=1730) [sender] rsync error: protocol incompatibility (code 2) at sender.c(174) [sender=2.6.9] I am hoping that with the additional log entries...someone might have an idea what is going on and the best way to get it back to normal. Theresa Peter Unix Team CSI - Data Services ISA-USAAC Theresa.Peter@usaac.army.mil (502) 626-0649 -----Original Message----- From: hashproduct@gmail.com [mailto:hashproduct@gmail.com] On Behalf Of Matt McCutchen Sent: Tuesday, September 04, 2007 2:31 PM To: Peter, Theresa M Ms CONT USAAC Cc: rsync@lists.samba.org Subject: Re: [U] Rsync Errors On 9/4/07, Peter, Theresa M Ms CONT USAAC <THERESA.PETER@usaac.army.mil> wrote:> I am seeing the following errors occasionally when doing an rsync > between servers (Solaris 9) at the local and remote site. Has anyone > seen these errors before or know what they are? > > rsync error: error in rsync protocol data stream (code 12) at > io.c(1122) [sender=2.6.9] rsync error: protocol incompatibility (code > 2) at io.c(954) [sender=2.6.9] rsync error: protocol incompatibility > (code 2) at io.c(960) [sender=2.6.9] rsync error: protocol > incompatibility (code 2) at sender.c(174) [sender=2.6.9] rsync error: > protocol incompatibility (code 2) at io.c(954) [sender=2.6.9] rsync > error: protocol incompatibility (code 2) at io.c(960) [sender=2.6.9] > rsync error: protocol incompatibility (code 2) at sender.c(174) > [sender=2.6.9] > > Both servers are using 2.6.9> We have had the networking group take a look at their switches and > routers bc we see "Broken Pipe" errors soon after we get one of the > above errors, but they are not seeing anything on their end.The "Broken Pipe" and the "error in rsync protocol data stream" are both aftermath of a previously occurring error. The other errors all mean that the sender received something invalid from the generator. That could indicate either a bug in rsync or corruption in the network connection. You could dump the data that each side sends and receives over the network using the "savetransfer" program that comes in support/ of the rsync source package ( http://rsync.samba.org/ftp/rsync/rsync-2.6.9.tar.gz ) to determine whether network corruption is occurring. Matt UNCLASSIFIED//// -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4995 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20070904/32ed1681/smime.bin
On 9/6/07, Peter, Theresa M Ms CONT USAAC <THERESA.PETER@usaac.army.mil> wrote:> We had just been running with WAS since April and never > had a problem prior to this. As far as the network group is concerned they > made no changes or upgrades to WAS. So it just seemed odd that out of the > blue we started to see problems.Bugs in compression algorithms tend to be very sensitive to the nature of the data being compressed. It's possible that the files you have been copying recently contain data sequences that trigger the bug in the WAS while files you copied previously did not. In any event, I recommend that you leave the WAS disabled and use rsync's built-in compression (-z option) if reducing network traffic is important. Matt