From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7+) Gecko/20020109 Description of problem: Upgrading the machine from which I synchronize files with rsync through ssh resulted in file updates problems. Version-Release number of selected component (if applicable): 2.4.6-8 How reproducible: Always Steps to Reproduce: 1. update to the latest rsync rsync-2.4.6-8 errata on the distant machine 2. run rsync -a -e ssh $* --delete --delete-after --exclude='nosync' \ servername:/var/www/* \ /var/www/ 3. get the error message :-( Actual Results: Many error messages : Warning: unexpected read size of 0 in map_ptr Expected Results: A correct synchronization of files. Additional info: This does not happen with rsync-2.4.6-5. Downgrading makes things work again. Also, upgrading the "client" machines makes the sync still work fine.
Ran from a client to a server both running rsync-2.4.6-8 : receiving file list ... done enigma/lbreakout2/ enigma/lbreakout2/lbreakout2-2.2-fr1.i386.rpm Warning: unexpected read size of 0 in map_ptr Warning: unexpected read size of 0 in map_ptr 1114516 (100%) enigma/lbreakout2/lbreakout2-2.2-fr1.src.rpm Warning: unexpected read size of 0 in map_ptr Warning: unexpected read size of 0 in map_ptr 1154599 (100%) enigma/lbreakout2/ wrote 19592 bytes read 2251167 bytes 57487.57 bytes/sec total size is 308556699 speedup is 135.88 After downgrading the server's rpm to rsync-2.4.6-5, it works fine but re-downloads the files (they were probably corrupted after the first download!) : receiving file list ... done enigma/lbreakout2/lbreakout2-2.2-fr1.i386.rpm 1114516 (100%) enigma/lbreakout2/lbreakout2-2.2-fr1.src.rpm 1154599 (100%) enigma/lbreakout2/ wrote 38498 bytes read 1131001 bytes 39644.03 bytes/sec total size is 308556699 speedup is 263.84
I'm having similar problems running the updated rsync over ssh. In one direction I get: unexpected EOF in read_timeout and the transfer fails. In the other direction I get a segmentation fault and the transfer fails.
FYI: this isn't only affecting SSH-based transfers.
*** This bug has been marked as a duplicate of 58874 ***