Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 133054 - rsync 2.6.8 is broken - unexpected tag 3 [sender]
Summary: rsync 2.6.8 is broken - unexpected tag 3 [sender]
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Other
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL: http://lists.samba.org/archive/rsync/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-11 11:54 UTC by Wernfried Haas (RETIRED)
Modified: 2006-05-13 21:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wernfried Haas (RETIRED) gentoo-dev 2006-05-11 11:54:12 UTC
rsync -av --exclude-from=/usr/local/etc/backupexclude --delete --delete-excluded / foo@bar::baz//
/some/files
/get/rsynced
unexpected tag 3 [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(828) [sender=2.6.8]

My backup script that rsyncs data to another box randomly craps out with this error message - seems to be the same problem as described in http://archives.free.net.ph/message/20060503.015807.6d41c961.en.html - there's also a patch in the reply in http://archives.free.net.ph/message/20060503.053039.38f0d4ad.en.html

Would be highly appreciated if someone could take a look at it as it currently breaks my backups - Thanks
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-05-11 13:00:57 UTC
Well, rsync-2.6.8 completely broke backuppc for me. Reverting to 2.6.0 fixes the problem.

rsync: writefd_unbuffered failed to write 124 bytes [sender]: Broken pipe (32)
rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)
rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)
...

and finally the infamous:
rsync error: error in rsync protocol data stream (code 12) at io.c(1119) [sender=2.6.8]

Noting that the above is localhost to localhost, so no version incompatibility issues etc.
Comment 2 SpanKY gentoo-dev 2006-05-11 20:38:36 UTC
why dont you test the patch and see if it actually addresses the issue

there's nothing for us to look at seeing as how *you* are the one experiencing the bug
Comment 3 Wernfried Haas (RETIRED) gentoo-dev 2006-05-12 09:43:51 UTC
I don't really understand what exactly you mean with comment #2, but the patch seems to work for me.
Still, i'm not an expert on rsync so it may prove useful to get another qualified opinion on this, especially considering rsync is a rather central package. That's why i asked if someone of you guys could look into it in the first place.
Comment 4 SpanKY gentoo-dev 2006-05-12 20:54:22 UTC
i didnt say you were

the guy who wrote the patch in the url you mentioned is an expert in rsync

you're the one experiencing the bug

pretty simple process:
 - user reports bug
 - expert fixes it
 - user verifies
 - distro maintainers include fix

we had the first parts done, but you needed to handle the third part

now that you have, 2.6.8-r1 in portage now with the fix
Comment 5 Rob Terhaar 2006-05-13 15:19:45 UTC
i know it's more of an upsteam issue- but r1 hasn't fixed BackupPC for me

If i create a new host, and do the initinal backup with 2.6.8r1 on the client i get the following message:

started full dump, share=/etc
xferPids 8463
xferPids 8463,8464
started full dump, share=/var/
xferPids 8465
dump failed: fileListReceive failed
link sugar.allovermedia.local
overflow: flags=0x6f l1=110 l2=1684631598, lastname=run/cgisock
overflow: flags=0x65 l1=114 l2=1886090089, lastname=




If i do the first full backup with 2.6.6, and then future backups with 2.6.8r1 there are no issues for me.
Comment 6 Jakub Moc (RETIRED) gentoo-dev 2006-05-13 21:06:21 UTC
(In reply to comment #5)
> i know it's more of an upsteam issue- but r1 hasn't fixed BackupPC for me

Please file a new bug.