Bug 2623

Summary:	rsync gives all kinds of errors during transfer
Product:	Mageia	Reporter:	Olav Vitters <olav>
Component:	RPM Packages	Assignee:	Olav Vitters <olav>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, stormi-mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	rsync	CVE:
Status comment:

Description Olav Vitters 2011-09-04 22:01:53 CEST

Description of problem:
While trying to mirror Mageia SRPMS and Mandriva SRPMS, I get various errors such as:
  WARNING: gimp-2.6.11-7.src.rpm failed verification -- update discarded (will try again).
  unexpected tag 73 [receiver]
  rsync error: error in rsync protocol data stream (code 12) at io.c(1139) [receiver=3.0.8]
  rsync: connection unexpectedly closed (117538 bytes received so far) [generator]
  rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.8]


Version-Release number of selected component (if applicable):
3.0.8-1

How reproducible:
WARNING: These commands will transfer a *lot* of data. I get errors for many files; usually the bigger ones (5MB+).
mkdir ~/mirror
cd ~/mirror
rsync -a --progress --delete-after rsync://ftp.acc.umu.se/mirror/mageia/distrib/cauldron/SRPMS/core/release/ cauldron-core
rsync -a --progress --delete-after rsync://ftp.nluug.nl/mandrivalinux/devel/cooker/SRPMS/main/release/ mandriva-main
rsync -a --progress --delete-after rsync://ftp.nluug.nl/mandrivalinux/devel/cooker/SRPMS/contrib/release/ mandriva-contrib

Steps to Reproduce:
1. Run above commands
2. See various error messages
3. Run it again. Some files (smaller ones) work, but usually it will still fail for the same files

This might be caused by something else (zlib, glibc, kernel); couldn't determine that though. My system is fully up to date with all the latest Cauldron packages. Tried recompiling the rsync package and a bm --without patches, but do not seem to help. I'm using 2 different mirrors and they both result in errors.

Comment 1 Samuel Verschelde 2011-10-01 03:18:10 CEST

As you are now the maintainer, this one is for you :)

CC: (none) => stormi
Assignee: bugsquad => olav

Comment 2 Marja Van Waes 2012-01-07 21:57:19 CET

pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED

@ Olav
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

Comment 3 Olav Vitters 2012-03-14 09:53:02 CET

local problem

Status: NEW => RESOLVED
Resolution: (none) => INVALID