repo-mirrorlist quality control?

Ralf Corsepius rc040203 at freenet.de
Wed Feb 25 13:15:30 UTC 2015


On 02/25/2015 01:49 PM, Richard Z wrote:
> Hi,
>
> when doing yum update in the last few weeks I am seeing thousands of errors like
>
> (1/2): _local/primary_db                                    | 3.4 MB  00:00
> updates/21/i386/primary_db     FAILED
> http://mirror.netcologne.de/fedora/linux/updates/21/i386/repodata/1f20884a6cce1ba8e28bb19e6dd364fe787906c1f0504c0d06e0fb1be8ab07ac-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> updates/21/i386/primary_db     FAILED
> http://mirror.fraunhofer.de/dl.fedoraproject.org/fedora/linux/updates/21/i386/repodata/1f20884a6cce1ba8e28bb19e6dd364fe787906c1f0504c0d06e0fb1be8ab07ac-primary.sqlite.bz2: [Errno 14] curl#18 - "transfer closed with 1521891 bytes remaining to read"
> Trying other mirror.
> (2/2): updates/21/i386/primary_db                           | 4.5 MB  03:26
> updates/21/i386/updateinfo     FAILED
> http://mirror.netcologne.de/fedora/linux/updates/21/i386/repodata/343502d43eec1d45e0f951d2c2d3373a146515d175e61c1609b44391f93cf08a-updateinfo.xml.gz: [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> updates/21/i386/pkgtags        FAILED
> http://mirror.netcologne.de/fedora/linux/updates/21/i386/repodata/6803dec7b564b291cead9d2b720a47bb73da52577e7f25e5b9df41582455f7a1-pkgtags.sqlite.gz: [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> (1/2): updates/21/i386/updateinfo                           | 644 kB  01:28
> (2/2): updates/21/i386/pkgtags                              | 1.4 MB  03:11
>
>
> and
>
> http://mirror.netcologne.de/fedora/linux/updates/21/i386/drpms/autocorr-en-4.3.5.2-11.fc21_4.3.6.2-3.fc21.noarch.drpm: [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
>
> While very rarely some other mirrors have problems, netcologne seems to be
> failing systematically for me.
>
> Is it just me?
No, it's not just you and it's not just the mirrors you list. Sometimes 
all Europe mirrors seem to be out of sync (This had happened 
yesterday.), with mirrormanager still reporting them as "functional".

Seems to me as if mirrormanager is dysfunctional, which then unhides 
deficiencies in yum/dnf and mock.

> Is there some place to report?
I have no idea, except that I am feeling quite sour about this, as well.


Ralf



More information about the devel mailing list