UNCLASSIFIED////
We were using compression on the network; through using a WAS device. We have turned that off and we are no longer seeing the problem. Why would compression cause these issues? If we turn the WAS (network compression) back on is this going to cause more issues. What do you mean by "the binary data protocol is no longer in sync"? Thanks Theresa Peter Unix Team CSI - Data Services ISA-USAAC [EMAIL PROTECTED] (502) 626-0649 -----Original Message----- From: Peter, Theresa M Ms CONT USAAC Sent: Wednesday, September 05, 2007 10:46 AM To: 'Wayne Davison'; 'rsync@lists.samba.org' Subject: [U] RE: RE: Rsync Errors UNCLASSIFIED//// We are not using the -z or --compress option. I have turned up the logging when running a job but I am not sure what I should be seeing. I have the log from both the machine that is pulling the data and the machine that the data is being pulled from. On the machine pulling data... It looks like that we get an "invalid file index" and then the job dies out. On the machine data is being pulled... I am seeing renaming of files, changing of modtimes, recv_files and recv_generator going at the same time. Then our final error: 2007/09/05 10:28:10 [15233] rsync: connection unexpectedly closed (165735 bytes received so far) [generator] 2007/09/05 10:28:10 [15233] rsync error: error in rsync protocol data stream (code 12) at io.c(453) [generator=2.6.9] 2007/09/05 10:28:10 [15233] _exit_cleanup(code=12, file=io.c, line=453): about to call exit(12) Any more ideas? What is going to be the best way to get us back on track? Should I restart the daemon, would that help anything; I wouldn't think so if it is a file problem with index? Theresa Peter Unix Team CSI - Data Services ISA-USAAC [EMAIL PROTECTED] (502) 626-0649 -----Original Message----- From: Wayne Davison [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 04, 2007 6:12 PM To: Peter, Theresa M Ms CONT USAAC Cc: rsync@lists.samba.org Subject: Re: [U] RE: Rsync Errors On Tue, Sep 04, 2007 at 05:56:11PM -0400, Peter, Theresa M Ms CONT USAAC wrote: > Invalid checksum length 39976960 [sender] > Invalid remainder length 39976960 [sender] > Invalid file index: 2046101527 (count=1730) [sender] These are all symptoms of the same problem -- the binary data protocol is no longer in sync. Whether it is caused by dropped bytes in the connection or a programatical error on rsync's part is the big question, and can't be determined by us. Are you using the -z (--compress) option? If so, try turning it off. ..wayne.. UNCLASSIFIED//// UNCLASSIFIED////
smime.p7s
Description: S/MIME cryptographic signature
-- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
