Hi All. I've had this problem with rsync, the solution to which has been really evasive to me. Any help would be appreciated. I'm running rsync 2.5.5 between 2 SCO boxes and get random "unexpected tag" errors. Sometimes the unexpected tag is positive, other times negetive, and a retry of rsync usually manages to work the second or third time round. The disks are identical in capacity on both systems (on http://rsync.samba.org/issues.html lists lack of diskspace causing a problem). On the "client" system I get these errors: [Thu Aug 15 23:22:56 2002] rsync: unexpected tag 79 [Thu Aug 15 23:22:56 2002] rsync: rsync error: error in rsync protocol data stream (code 12) at io.c(298) [Thu Aug 15 23:22:56 2002] rsync: connection unexpectedly closed (3495 bytes read so far) [Thu Aug 15 23:22:56 2002] rsync: rsync error: error in rsync protocol data stream (code 12) at io.c(150) While on the "server" system I get: Aug 15 23:27:12 abacus5 rsyncd[9449]: rsync: error writing 4096 unbuffered bytes - exiting: Broken pipe Aug 15 23:27:12 abacus5 rsyncd[9449]: rsync error: error in rsync protocol data stream (code 12) at io.c(463) Thanking you in advance. Bradley Kite Software Developer/Data Management Specialist alchemetrics - smarter data, faster Tel: 0118 902 9043 (direct line) Email: bradley.kite@alchemetrics.co.uk Web: http://www.alchemetrics.co.uk QuickCounts Demo: http://www.quickcounts.co.uk ************************************************************************************** ALCHEMETRICS LIMITED (ALCHEMETRICS) Mulberry Park, Fishponds Road, Wokingham, Berkshire, RG41 2GX Tel: +44 (0) 118 902 9000 Fax: +44 (0) 118 902 9001 This e-mail is confidential and is intended for the use of the addressee only. If you are not the intended recipient, you are hereby notified that you must not use, copy, disclose, otherwise disseminate or take any action based on this e-mail or any information herein. If you receive this transmission in error, please notify the sender immediately by reply e-mail or by using the contact details above and then delete this e-mail. Please note that e-mail may be susceptible to data corruption, interception and unauthorised amendment. Alchemetrics does not accept any liability for any such corruption, interception, amendment or the consequences thereof. **************************************************************************************
Hi everyone. I'm running an rsync (2.5.6-cvs) between 2 SCO Unix boxes (SCO_SV 3.2 5.0.5 i386), and keep getting aparently random "unexpected tag" errors. If I re-run rsync when this error occurs everything will usually go OK (even if it takes 2 or 3 runs on the same data...) Could somebody please explain what a "tag" is (looking through the code it's derived from the first 4bytes of each read_unbuffered() call and I think its to do with multiplexing, but what are all of the multiplexing "sub-channels" used for? (seem to be defined as FNONE=0, FERROR=1, FINFO=2, FLOG=3). Has any body else encountered these errors? Any advise much appreciated! Bradley Kite Software Developer/Data Management Specialist alchemetrics - smarter data, faster Tel: 0118 902 9043 (direct line) Email: bradley.kite@alchemetrics.co.uk Web: http://www.alchemetrics.co.uk QuickCounts Demo: http://www.quickcounts.co.uk ************************************************************************************** ALCHEMETRICS LIMITED (ALCHEMETRICS) Mulberry Park, Fishponds Road, Wokingham, Berkshire, RG41 2GX Tel: +44 (0) 118 902 9000 Fax: +44 (0) 118 902 9001 This e-mail is confidential and is intended for the use of the addressee only. If you are not the intended recipient, you are hereby notified that you must not use, copy, disclose, otherwise disseminate or take any action based on this e-mail or any information herein. If you receive this transmission in error, please notify the sender immediately by reply e-mail or by using the contact details above and then delete this e-mail. Please note that e-mail may be susceptible to data corruption, interception and unauthorised amendment. Alchemetrics does not accept any liability for any such corruption, interception, amendment or the consequences thereof. **************************************************************************************