Need help?

Our experts have had an average response time of 13.14 minutes in February 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

YUM Error Downloading Packages – how we fix it?

by | Nov 22, 2019

Not able to download packages with yum due to the error ‘[Errno 256] No more mirrors to try’? We can help you with it.

Usually, corrupted yum cache or repo directory ends up in this error. A few file cleanups can easily fix this.

This can also occur due to an outdated whitelist of the Public CIDR list.

At Bobcares, we often fix yum errors, as a part of our Server Management Services.

Today, let’s have a look into this yum error. And see how our Support Engineers fix this.

 

Why does yum downloading packages end up in error?

We often use yum to install packages and dependencies in a single command. However, sometimes we have seen this yum updates ending up with an error.

Mostly, this happens due to errors with yum cache, local files in the repository folder, outdated firewall rules, etc.

Let’s check out how our Support Engineers fix this error in each case.

 

How we fix the yum error in downloading packages?

The error message while installing the FTP package appears as,

yum error downloading packages in Linux.

Now let’s have a look at each reason and its fix.

 

1. Clear yum cache to download packages

Old cache in the system can cause errors while downloading packages. Hence our Support Engineers delete the cache using the command,

rm -rf /var/cache/yum/*

In addition, we also delete the metadata for the enables repositories. For this, we use the command,

yum clean metadata

Later, we clean up the yum folder using the command,

yum clean all

Finally, we check the yum update again. Thereby, we ensure to fix the error.

 

2. Check repository to fix yum error

In some servers, the yum repository contains corrupted files. And accessing these repositories while updating can cause errors. So our Support Engineers check the folder yum.repos.d

Initially, we list the files using the command,

ll /etc/yum.repos.d

Later we check the system registry. Our Experts check the files under both RHN classic and RHSM. And removes the error causing local repositories. Later, we check if the update is running successfully.

 

3. Network access to download packages

Similarly, network access is important for yum updates. So, we check the access to the repository URL by ping.

In addition, we also ensure to whitelist the Public CIDR list for Red Hat. Because outdated whitelist restricts access to the CDN can result in errors.

Usually, yum download the packages using the base URL in the config file. This URL is cdn.redhat.com. Basically, there are multiple servers resolving to this address.

So we whitelist these IPs listed in the Public CIDR list.

 

[Need assistance in fixing yum errors? – We are available 24/7]

 

Conclusion

In short, yum error downloading packages occur due to corrupted cache or repository. Another possible reason is network access denial due to the firewall in the system. Today, we saw how our Support Engineers fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF