Why does yum return error: [Errno 256] No more mirrors to try ?

Solution Verified - Updated -


  • Red Hat Enterprise Linux 5 and later
  • Red Hat Customer Portal
  • Red Hat Subscription Management (RHSM)
  • Red Hat Satellite


  • yum update fails with the error : [Errno 256] No more mirrors to try
  • yum update fails with :-
Error Downloading Packages:
InstallMedia: [Errno 256] No more mirrors to try.
  • yum fails with :
Error Downloading Packages:
ftp-0.17-35.el5.x86_64:failure:ftp-0.17-35.el5.x86_64.rpm from Red5repo55:[Errno 256] No more mirrors to try. [[6]]" (code -1) Packages Scheduled
  • yum fails with :
Downloading Packages:
https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/supplementary/os/Packages/java-1.6.0-ibm- [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
Error Downloading Packages:
  1:java-1.6.0-ibm- failure: Packages/java-1.6.0-ibm- from rhel-6-server-supplementary-rpms: [Errno 256] No more mirrors to try.


  • Check the network connectivity. If you are using IP addresses to configure firewall whitelist for access to the content delivery network (CDN), please ensure they're updated based on this list: Public CIDR Lists for Red Hat (IP Addresses for cdn.redhat.com)

  • Check what files are present under /etc/yum.repos.d directory by:-

# ll /etc/yum.repos.d
  • If the system is registered to RHN Classic, only rhel-source.repo should be present under /etc/yum.repos.d/.
    If the system is registered with Red Hat Subscription Manager (RHSM) via subscription-manager, rhel-source.repo and 'redhat.repo' are present.
    If any local repositories, or any other media repositories are present, remove them by :-
# rm -rf /etc/yum.repos.d/<local or other repository name>
  • Remove old yum cache from system by running following commands:
# rm -fr /var/cache/yum/*
# yum clean all
  • Check if you can list the valid repositories by :-
# yum repolist

Root Cause

  • Possible reasons for this issue:
    1. Corrupted yum cache.
    2. Inaccessibility of a repository URL from the system due to network related issues.
    3. Presence of customized or other media repositories.
    4. Outdated whitelist when using IP-based Firewall configuration to access Red Hat's Content Delivery Network (CDN).

Diagnostic Steps

  • Check the accessibility of the repository URL in the system/network.
# ping URL
  • Check the repositories under /etc/yum.repos.d
ll /etc/yum.repos.d
  • Collect a sosreport of the affected system.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.


Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.