Mirror Failure

Home » CentOS » Mirror Failure
CentOS 11 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.



11 thoughts on - Mirror Failure

  • No. Was that all it took? Of the thousand answers found on Google that didn’t work, that wasn’t mentioned once.

    If you could explain why that would work I’d be eternally grateful & all ears.



  • Phil Dobbin wrote:

    Did you try it?

    Your google fu needs work. It should have found a zillion hits.

    What happens is that yum caches the mirror addresses, and uses the cached addresses, rather than look them up every bloody time. Clearing all, including the cache, will force it to look Out There again.


  • Well, maybe my “Google fu” is off but I just posted the error message I
    received as I normally do when I hit a problem but didn’t get one clue back about ‘yum clean all’. I know: what an amateur.

    Anyway all’s well now, my client’s happy, he’s got all his machines online whether CentOS, Ubuntu or Amiga, I know what to do next time &
    the so the story’s told.

    Thanks to everybody for their help. Have a good one,



  • Just curious, would this apply to any “other” rpm-based Linux distro? as well….(Fedora….Scientific?….etc?)

    EGO II