samba-bugs at samba.org
2013-Dec-17 18:06 UTC
[Bug 10332] New: sync won't talk to rsync-3.1.0
https://bugzilla.samba.org/show_bug.cgi?id=10332 Summary: sync won't talk to rsync-3.1.0 Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: mal at gromco.com QAContact: rsync-qa at samba.org I have a client copying server data for backup using rsync over ssh rsync --numeric-ids --partial -az --rsh=ssh --del --compress root at 1.2.3.4:/home_server_path/ /path_to_local_backup/ the problem: if server rsync is compiled from rsync-3.0.9-12.fc19.src.rpm then any client rsync version works fine (rsync-3.0.9, rsync-3.1.0-2 , rsync-3.1pre1) If server rsync is compiled from rsync-3.1.0-2.fc21.src.rpm then no client rsync works to completion. Typically transfer starts, go for 1-2 hours, then fails with error message like this: --------- client 3.1.0pre1 errors---------- inflate returned -3 (0 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(557) [receiver=3.1.0pre1] rsync: connection unexpectedly closed (2454943 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [generator=3.1.0pre1] inflate returned -3 (0 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(557) [receiver=3.1.0pre1] rsync: [generator] write error: Broken pipe (32) rsync error: error in socket IO (code 10) at io.c(837) [generator=3.1.0pre1] ------------ client 3.0.9 errors ---------- inflate returned -3 (0 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(548) [receiver=3.0.9] rsync: connection unexpectedly closed (1575 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [generator=3.0.9] inflate returned -3 (0 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(548) [receiver=3.0.9] rsync: connection unexpectedly closed (1403 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [generator=3.0.9] -------------------- see https://bugzilla.redhat.com/show_bug.cgi?id=1043965 for original report -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=10332 Wayne Davison <wayned at samba.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Wayne Davison <wayned at samba.org> 2013-12-23 17:21:48 UTC --- A "connection unexpectedly closed" means that the other side went away (or something in the middle closed the connection), so you need to figure out what is happening that causes the connection to close. Some suggestions for what to do are on the http://rsync.samba.org/issues.html page (e.g. see the rsync-debug script). -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=10332 --- Comment #2 from mal at gromco.com 2013-12-23 17:31:26 UTC --- Correct, the rsync-3.1.0-2.fc21.src.rpm running on the server unexpectedly closed connection in the middle of a transfer. And client rsync reported this. I will try look how to get server rsync debug. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=10332 --- Comment #3 from Orion Poplawski <orion at cora.nwra.com> 2014-03-18 16:18:28 UTC --- I'm guessing a dupe of bug 10372? -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=10332 --- Comment #4 from George <gfedorov at unimelb.edu.au> --- Had a similar issue with rsync 3.1.0 on the server, building 3.1.1 with internal lib solved the problem; therefore -- could indeed be a dup of bug 10372. -- You are receiving this mail because: You are the QA Contact for the bug.
Possibly Parallel Threads
- [Bug 11215] New: compression/zlib errors discard the zlib error message
- Rsync 3.1.0pre1 released
- Rsync 3.1.0pre1 released
- [Bug 10372] New: rsync 3.10 error in protocol data stream while rsync 3.0.9 runs through
- [Bug 10497] New: rsync fails to sync certain sparse file combinations with compression