Bug 959824

Summary: rsync fails with "error in rsync protocol data stream (code 12) at io.c(600)"
Product: Red Hat Enterprise Linux 6 Reporter: Nilesh Parmar <nparmar>
Component: rsyncAssignee: Michal Luscon <mluscon>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: richard.a.karhuse
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-07 01:34:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1002711    
Attachments:
Description Flags
rsync coredump none

Description Nilesh Parmar 2013-05-06 02:37:43 UTC
Created attachment 743965 [details]
rsync coredump

Description of problem:

rsync crashes with below error:

rsync: connection unexpectedly closed (633 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [generator=3.0.6]


Version-Release number of selected component (if applicable):
rsync-3.0.6-9.el6

How reproducible:
Happens while dealing with larger data set

Steps to Reproduce:

rsync -abRrptgoDXA --stats --delete --force --rsync-path=/tmp/rrsync --backup-dir=$destpath --rsh"sudo -u backupuser ssh -p port sshopts" --files-from=source_files --exclude-from=excludes backupuser@machine:/ destination
  
Actual results:
rsync crashes

Expected results:
rsync should not crash

Additional info:

KBase article: rsync errors out with inflate (token) returned -5 
https://access.redhat.com/site/solutions/84723

It mentions that the above issue occurs for rsync versions prior to 3.0.6-9.el6. 

But customer has rsync-3.0.6-9.el6.x86_64 package on his system.

# gdb -c coredump /usr/bin/rsync 

+++++++++++++++++++++++++++++++++++++++++++++++++
Core was generated by `rsync -abRrlptgoDXA --stats --sockopts=SO_SNDBUF=4194304,SO_RCVBUF=4194304,IP_T'.
Program terminated with signal 6, Aborted.
#0  0x00007f8ecd6588a5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64	  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
+++++++++++++++++++++++++++++++++++++++++++++++++

(gdb) bt
#0  0x00007f8ecd6588a5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007f8ecd65a085 in abort () at abort.c:92
#2  0x00007f8ecd6967b7 in __libc_message (do_abort=2, fmt=0x7f8ecd77df80 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:198
#3  0x00007f8ecd69c0e6 in malloc_printerr (action=3, str=0x7f8ecd77c06f "free(): invalid pointer", ptr=<value optimized out>) at malloc.c:6311
#4  0x00000000004339e9 in uncache_tmp_xattrs () at xattrs.c:787
#5  0x0000000000421875 in keep_backup (fname=0x7fff8dd041d0 "var/lib/upgrade/backup/riak-originals/originals/bucketkeys.keys") at backup.c:369
#6  make_backup (fname=0x7fff8dd041d0 "var/lib/upgrade/backup/riak-originals/originals/bucketkeys.keys") at backup.c:384
#7  0x000000000040b7d6 in finish_transfer (fname=0x7fff8dd041d0 "var/lib/upgrade/backup/riak-originals/originals/bucketkeys.keys", 
    fnametmp=0x7fff8dd021d0 "var/lib/upgrade/backup/riak-originals/originals/.bucketkeys.keys.9Qgr2r", fnamecmp=0x7fff8dd041d0 "var/lib/upgrade/backup/riak-originals/originals/bucketkeys.keys", 
    partialptr=0x0, file=0x7f8ecdee5ba0, ok_to_set_time=1, overwriting_basis=1) at rsync.c:568
#8  0x00000000004130ad in recv_files (f_in=6, local_name=0x0) at receiver.c:736
#9  0x000000000041c3e7 in do_recv (f_in=6, f_out=5, local_name=0x0) at main.c:774
#10 0x000000000041c732 in client_run (f_in=6, f_out=5, pid=24331, argc=<value optimized out>, argv=0x677248) at main.c:1067
#11 0x000000000041d59d in start_client (argc=2, argv=0x677240) at main.c:1274
#12 main (argc=2, argv=0x677240) at main.c:1501

Comment 5 Andrius Benokraitis 2013-10-07 01:34:25 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6, and will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.