samba-bugs@samba.org
2009-Jan-14 02:58 UTC
DO NOT REPLY [Bug 6032] New: error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 Summary: error in rsync protocol data stream Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: rmang@lexiconn.com QAContact: rsync-qa@samba.org Command: /usr/bin/rsync -aze /usr/local/ssh/bin/ssh --hard-links --force --ignore-errors --numeric-ids --delete --exclude=/sys --exclude=/proc --exclude=/var/named/chroot/proc --exclude=/home4 --exclude=/home5 --exclude=/backup --exclude=/var/log --exclude=/home/logs --exclude=/home2/logs/ $server:/ /home/backup/$short The error happens at the same spot during the rsync copy: Read from remote host $server: Connection reset by peer rsync: connection unexpectedly closed (16892096 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [receiver=3.0.4] rsync: connection unexpectedly closed (408 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(632) [generator=3.0.4] -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
samba-bugs@samba.org
2009-Jan-14 04:06 UTC
DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 ------- Comment #1 from rmang@lexiconn.com 2009-01-13 22:06 CST ------- Created an attachment (id=3875) --> (https://bugzilla.samba.org/attachment.cgi?id=3875&action=view) rsync-debug output (last 200 lines) This is the last 200 lines from the 10 MB rsync-debug output file. I was not able to get a core dump. If you need anything else, please let me know. The rsync fails on the same file/location every time. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
samba-bugs@samba.org
2009-Jan-14 05:09 UTC
DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 matt@mattmccutchen.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #2 from matt@mattmccutchen.net 2009-01-13 23:10 CST ------- It looks like neither rsync process intentionally closed the connection, so it must have been dropped by the network. This is not a bug in rsync. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
samba-bugs@samba.org
2009-Jan-14 05:25 UTC
DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 ------- Comment #3 from rmang@lexiconn.com 2009-01-13 23:26 CST ------- ok, just seems strange that the rsync fails every time on the same dovecot.patched.tar.gz file. Any pointers on how to t/s would be appreciated. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
samba-bugs@samba.org
2009-Jan-16 00:02 UTC
DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 ------- Comment #4 from matt@mattmccutchen.net 2009-01-15 18:02 CST ------- That is strange, but the output does seem to indicate pretty clearly that rsync is not the thing closing the connection. It's possible that the file is triggering a data-dependent bug in ssh or even the network (but that seems unlikely because ssh would be encrypting with a different random key each time). In any case, you could see whether rsync fails in the same way when you do any of the following: - Remove the -z option. - Transfer using an rsync daemon instead of ssh (unless the file is secret). - Transfer the file between a different pair of hosts. - Make a copy of the file, modify it slightly (e.g., modify a few bytes or slightly lengthen or shorten it), and transfer that. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
Reasonably Related Threads
- FILE CACHE/LOCKING DOES NOT WORK
- DO NOT REPLY [Bug 5795] New: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4]
- pop3_lock_session question
- DO NOT REPLY [Bug 5854] New: --del (+old protocol?) sometimes leads to "double free" crashes
- DO NOT REPLY [Bug 5894] New: Incompatible library version