Mirror Problem

Home » CentOS » Mirror Problem
CentOS 4 Comments

Hi, all.

I was getting:

[Errno 14] PYCURL ERROR 6 – “Couldn’t resolve host ‘mirror01.th.ifl.net'”
Trying other mirror. ftp://ftp.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/6/x86_64/repodata/c60f7c3ee6f9a4902d5ce9dd181a84ca684bba1a1df1c612702c7c6760a04645-filelists.sqlite.bz2:
[Errno 14] PYCURL ERROR 6 – “Couldn’t resolve host ‘ftp.mirrorservice.org'”
Trying other mirror. ftp://ftp.fedora.is/pub/epel/6/x86_64/repodata/c60f7c3ee6f9a4902d5ce9dd181a84ca684bba1a1df1c612702c7c6760a04645-filelists.sqlite.bz2:
[Errno 14] PYCURL ERROR 6 – “Couldn’t resolve host ‘ftp.fedora.is'”
Trying other mirror. ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/epel/6/x86_64/repodata/c60f7c3ee6f9a4902d5ce9dd181a84ca684bba1a1df1c612702c7c6760a04645-filelists.sqlite.bz2:
[Errno 14] PYCURL ERROR 6 – “Couldn’t resolve host ‘ftp.funet.fi'”
Trying other mirror. ftp://mirrors.fedoraproject.org.uk/dl.fedoraproject.org/pub/epel/6/x86_64/repodata/c60f7c3ee6f9a4902d5ce9dd181a84ca684bba1a1df1c612702c7c6760a04645-filelists.sqlite.bz2:
[Errno 14] PYCURL ERROR 6 – “Couldn’t resolve host
Trying other mirror. Error: failure:
from epel: [Errno 256] No more mirrors to try.
You could try using –skip-broken to work around the problem`

every time I ran `sudo yum update’. This happened on Fedora 17 also. I’ve had to switch both machines to Ubuntu because I need working machines.

I’ve Googled this extensively & changed my nameservers, commented out relevant lines in the configs, etc, etc but no luck so far. Ubuntu works fine & I have no network problems (two HP ProCurves 2124s working normally over the rest of the network: 17 machines).

Is there a workaround for this as I need a working CentOS box.

Any help appreciated.



4 thoughts on - Mirror Problem

  • Hello, I have thousands of this messages on my servers ??

    Is this a Problem on my site or is the infrastructure broken??

    Could not get metalink https://mirrors.fedoraproject.org/metalink?
    repo=epel-7&arch=x86_64 error was
    14: HTTPS Error 503 – Service Unavailable

    Thanks for a answer,

  • Not just you. I’ve seen that error on my hourly yum check on my personal Linode server, though I haven’t been in a big hurry to investigate yet as it only appears once or twice a day.

  • You might want to try a “yum check-update” manually (maybe only against the epel repo). If you get an error try a “yum clean all” and then try the “… check-update” again. I didn’t have a problem just now with the epel repo, but then again always start my checks with a
    “clean all”.

    Of course this isn’t a CentOS repo, so if you continue to have problems a report would need to be made with epel/fedora.

    As a note/side question … I’ve never understood why this script
    (which I never leave installed) is in “cron.hourly”. I would think that “cron.daily” would be a sufficient frequency. This appears to be a CentOS “touched” script so can’t tell if upstream puts it in hourly or CentOS does.

  • Hello, from the Fedora side of Infrastructure. We have been trying to get the 503 error rate down in the last six months and thought we had licked it with recent changes. We had moved down the error rate to
    80,000 bad requests per day out of 13.5 million total ones which actually is a creep up from what we had last month. Most of the requests every day happen in the time frame of XX:00 -> XX:15 of every hour. Every proxy seems to give about 100 per day but 2 proxies seem to have had docker problems and have been each contributing 32,000 to
    38,000 503’s.

    We did find an error in the docker restart script which hopefully will drop this further. We are still evaluating why just those 2 proxies have so many more and will let you know what is found.

    Thank you for your patience.

    Stephen J Smoogen.