= bug description = The testing URL of this mirror hasn't been updated since 10/07/14
ftp://mirror.as24220.net/pub/fedora/linux/updates/testing/21/x86_64/repodata/
= bug analysis = Not really sure. Possibly out of sync mirror. Each time I use dnf, it fails at this one for F21 updates-testing. Could also be a dnf bug, but I can't be sure at the moment.
= fix recommendation = Probably ask the mirror admin to check the mirror?
I have disabled the mirror and added the mirror admin in CC to have a look why the content may have become outdated.
Looking at
http://mirror.as24220.net/pub/fedora/linux/updates/testing/21/x86_64/repodata/
it seems the mirror is up to date again. Closing the ticket.
Hrm, yeah, looks up to date, but dnf still errors out on this mirror. This is what I get:
{{{ [asinha@localhost ~]$ sudo dnf list freemedforms timer: config: 8 ms cachedir: /var/cache/dnf/x86_64/21 Loaded plugins: kickstart, builddep, needs-restarting, copr, playground, generate_completion_cache, download, Query, protected_packages, noroot, debuginfo-install DNF version: 0.6.1 Command: dnf list freemedforms Installroot: / Releasever: 21 Base command: list Extra commands: [u'freemedforms*'] repo: downloading from remote: updates-testing, _Handle: metalnk: https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f21&arch=x86_64, mlist: None, urls []. Cleaning up.x86_64 - Test Updates 98% [==============================================================- ] 483 kB/s | 2.8 MB 00:00 ETA Error: Failed to synchronize cache for repo 'updates-testing' from 'https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f21&arch=x86_64': Yum repo downloading error: Downloading error(s): repodata/f797b1d406b6c097cedc251947d6bf850cdfb630f7ee9c3050f43bc542885547-comps-f21.xml.gz - Download failed: Curl error: Failure when receiving data from the peer for ftp://mirror.as24220.net/pub/fedora/linux/updates/testing/21/x86_64/repodata/f797b1d406b6c097cedc251947d6bf850cdfb630f7ee9c3050f43bc542885547-comps-f21.xml.gz; repodata/222aeb6f7810ee54110af89dfe45eddb0f28d4c92fe1ab55e910b07f0268216a-primary.xml.gz - Download failed: Curl error: Failure when receiving data from the peer for ftp://mirror.as24220.net/pub/fedora/linux/updates/testing/21/x86_64/repodata/222aeb6f7810ee54110af89dfe45eddb0f28d4c92fe1ab55e910b07f0268216a-primary.xml.gz; repodata/63e789fc787e4f6286aac261692d18c518bfafbd7af25470cbf0f786ce7ec552-prestodelta.xml.gz - Download failed: Curl error: Failure when receiving data from the peer for ftp://mirror.as24220.net/pub/fedora/linux/updates/testing/21/x86_64/repodata/63e789fc787e4f6286aac261692d18c518bfafbd7af25470cbf0f786ce7ec552-prestodelta.xml.gz
}}}
Happens with the updates repo too. Not sure what's causing the issue here:
{{{ Cleaning up.x86_64 - Updates 0% [ ] --- B/s | 0 B --:-- ETA Error: Failed to synchronize cache for repo 'updates' from 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f21&arch=x86_64': Yum repo downloading error: Downloading error(s): repodata/401dc19bda88c82c403423fb835844d64345f7e95f5b9835888189c03834cc93-filelists.xml.gz - Download failed: Curl error: Failure when receiving data from the peer for ftp://mirror.as24220.net/pub/fedora/linux/updates/21/x86_64/repodata/401dc19bda88c82c403423fb835844d64345f7e95f5b9835888189c03834cc93-filelists.xml.gz; repodata/52741e070db97c6420998825ac77aa2d4b03c51660d1007d5b617338e6366f69-prestodelta.xml.gz - Download failed: Curl error: Failure when receiving data from the peer for ftp://mirror.as24220.net/pub/fedora/linux/updates/21/x86_64/repodata/52741e070db97c6420998825ac77aa2d4b03c51660d1007d5b617338e6366f69-prestodelta.xml.gz; repodata/dabe2ce5481d23de1f4f52bdcfee0f9af98316c9e0de2ce8123adeefa0dd08b9-primary.xml.gz - Download failed: Curl error: Failure when receiving data from the peer for ftp://mirror.as24220.net/pub/fedora/linux/updates/21/x86_64/repodata/dabe2ce5481d23de1f4f52bdcfee0f9af98316c9e0de2ce8123adeefa0dd08b9-primary.xml.gz
Are you behind a proxy or the like?
Can you manually get anything from the ftp link?
The mirror looks up to date to me.
Can you re-open this if you still see issues with it?
Login to comment on this ticket.