Red Hat Bugzilla – Bug 471182
rsync errors: unexpected tag 3 [sender]
Last modified: 2015-03-04 18:56:38 EST
Description of problem:
I am trying to synchronize several virtual guests between two rhel5.2 servers. Sometimes rsync process fails in certain virtual guests and another times fails with others.
Rsync command that I use to synchronize between two hosts is:
rsync --stats -avH --delete --delay-updates /vmachines/srvdns 172.26.0.11::vmachines/
Version-Release number of selected component (if applicable):
Every time that I launch described process.
Steps to Reproduce:
1. Launch rsync command
Error reported from client side:
Running rsync: Wed Nov 12 01:25:31 CET 2008
+ rsync --stats -avH --delete --delay-updates /vmachines/srvdns 172.26.0.11::vmachines/
building file list ... done
unexpected tag 3 [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(828) [sender=2.6.8]
Error reported from server side:
2008/11/12 00:25:42  2008/11/12 00:25:42: host UNKNOWN (172.26.0.10) recv srvdns/SrvDNS.nvram (8684 bytes). Total 88 bytes.
2008/11/12 00:25:42  rsync: read error: Connection reset by peer (104)
2008/11/12 00:25:42  rsync error: error in rsync protocol data stream (code 12) at io.c(614) [receiver=2.6.8]
2008/11/12 00:25:42  rsync: connection unexpectedly closed (486 bytes received so far) [generator]
2008/11/12 00:25:42  rsync error: error in rsync protocol data stream (code 12) at io.c(463) [generator=2.6.8]
Created attachment 334665 [details]
This bug has been fixed in rsync 2.6.9 (bug #339971 to rebase rsync to 2.6.9), in the mean time the patch here is backported from rsync 2.6.9 code.
This is a slightly different patch from the one attached to bug #206536 for FC5 which seems to be incomplete.
Thanks for the info about this being fixed in rsync 2.6.9. That helps!
This bug seems to still exists in:
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Not good... NOT good...
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.