Errno 14 pycurl error 22 the requested url returned error 404 not found

Обновлено: 20.06.2020
Опубликовано: 13.11.2016

Описание

При попытке выполнить команды yum update или yum install в CentOS консоль выдает ошибку [Errno 14] PYCURL ERROR 22 — «The requested URL returned error: 404»

Причина

Пути в кэше одного из репозирориев устарели и ведут на страницы, которых больше не существует (об этом говорит строка «The requested URL returned error: 404»).

Это могло произойти по причине использования Linux, который долгое время не обновлялся.

Решение

1. Просто очистите кэш следующей командой:

yum clean all

и выполните команду по обновлению:

yum update

2. Если этого окажется недостаточно, смотрим список подключенных репозиториев:

yum repolist -v

… и отключаем их по одному.

Например, для отключения репозитория epel:

Repo-id            : epel
…
Repo-filename      : /etc/yum.repos.d/epel.repo

… открываем файл:

vi /etc/yum.repos.d/epel.repo

Находим опцию enabled и меняем ей значение на 0:

…
enabled=0
…

После отключения каждого из репозиториев пробуем команду:

yum update

В чем была проблема?

Если вам удалось решить проблему, поделитесь своим опытом для других. Что помогло:

* в процентах показаны результаты ответов других посетителей.

Are you getting yum PycURL error 22 in between an important update?

Yum errors always need an immediate fix as it affects package management in the servers.

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

Today, let’s have a quick look at yum. We’ll also see how our Support Engineers fix the PycURL error.

Reasons for yum PycURL error 22?

Yum aka Yellowdog Updater, Modifier is a popular package manager in Red Hat Linux. But yum works with the Red Hat Package Manager (RPM). Hence this works in the Red Hat Linux variant like CentOS.

In addition, yum also install dependencies of packages. But yum command often end up in errors.

Today, we’ll discuss the possible reasons for PycURL error 22.

The possible reasons are:

• Unsupported repository
• Misconfigured proxy server
• Yum cache

Now, let’s see the fixes for this error.

How we fix the yum PycURL error 22?

Our Support Engineers with expertise in Server Administration fixes yum errors quite often. Let’s see how we fix this.

1. yum error 22 due to unsupported repository

Recently, our customer had PycURL error 22 while yum upgrade in the CentOS system. Our Support Engineers re-executed the command to troubleshoot the error. The upgrade terminated at one of the repositories with an error message.

[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found." Trying other mirror.

Hence we checked the repo file. For this, we open the yum repo file. Editing these files need root access.

vi /etc/yum.repo.d

Further, we checked for the module which caused the error. And we disabled it.

But this didn’t fix the error.  So, we removed this manually.

Finally, we used the command to clean the yum.

yum clean all

And this fixed the error.

2. Correct the proxy setting

In some cases, the corrupted proxy configuration causes errors.

Today, proxy servers are important security measures. That is, proxy servers acts as a security layer between the server and the Internet.

So, our Support Engineers check the config file. We edit the config file as a root user.

vi /etc/yum.conf

Here we fill the proxy setting and save the file.

Some customers have subscription managers like RHSM. In such cases, we update the proxy setting in their config file. For instance, for RHSM we update the/etc/rhsm/rhsm.conf file.

3. Clear yum cache to fix PycURL error 22

Similarly, a corrupted local machine cache can also cause PycURL error. To fix this, we clear the yum cache using the command,

yum clear all

If the error persists, then our Support Engineers clear the cache folder.

rm -rf /var/cache/yum/*

Last but not least, connection errors or outdated OS versions can end up in errors. So, we check the system status and upgrade it if needed.

[Still having trouble in fixing yum errors? – We’ll help you.]

Conclusion

In short, yum PycURL error 22 occur due to many reasons. The most common reasons are an unsupported repository, misconfigured proxy server, yum cache and system status. Today, we saw how our Support Engineers fixed this error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

How to Fix: Yum [Errno 14] PYCURL ERROR 22 — 404 Not Found

Infopackets Reader Steve T. writes:

I am running Centos 6 32-bit (i386) on a virtual machine and recently I started having ‘PYCURL ERROR 22’ every time I use ‘yum list updates’ or ‘yum -y update’ to list and download updates. The error message says ‘[Errno 14] PYCURL ERROR 22 — The requested URL returned error: 404 Not Found‘. I have gone to the wiki.centos.org/yum-errors as the error message suggests, but have not been able to find a solution to this problem. Can you help? «

I asked Steve if he would like me to connect to his virtual machine using my remote desktop support service in order to have a closer look at the problem, and he agreed. Below I will discuss my findings.

How to Fix: Yum [Errno 14] PYCURL ERROR 22 — 404 Not Found

As the centos.org wiki suggests, the first thing to do is to clear the yum cache as it may be corrupt, which will result in the PYCURL ERROR 22. To do so, open a terminal window / SSH and enter in the following:

yum clean all
rm -rf /var/cache/yum/*

If that does resolve your problem, please have a closer look at the error message. In Steve’s case it was the repo.ius.io mirror which was failing, as noted in the sample output below. In order to fix it, I went to the /etc/yum.repos.d directory and modified the ius.repo file in order to disable it.

Here is the sample output:

yum list updates

Loaded plugins: fastestmirror
Repository remi-safe is listed more than once in the configuration
Repository remi-php70 is listed more than once in the configuration
Loading mirror speeds from cached hostfile

* base: mirror.layeronline.com
* extras: mirror.layeronline.com
* remi: rpms.remirepo.net
* remi-php71: rpms.remirepo.net
* remi-safe: rpms.remirepo.net
* rpmforge: mirror.bacloud.com
* updates: mirror.layeronline.com

base | 3.7 kB 00:00
extras | 3.3 kB 00:00

https ://repo.ius.io/6/i386/repodata/repomd.xml : [Errno 14] PYCURL ERROR 22 — «The requested URL returned error: 404 Not Found»

Trying other mirror.

To address this issue please refer to the below wiki article

Disable Repository to Fix ‘PYCURL ERROR 22’

If you note the above output (red bold text), it lists the URL that is causing the error (repo.ius.io). To fix the error you need to disable the repository via its configuration file, but this is really only a temporary fix to the issue as it does not replace the broken repository.

For the record, I attempted to open https: //repo.ius.io/6/i386/repodata/repomd.xml via the browser and it results in a 404 (file not found). After a bit more research, it appears that repo.ius.io has removed all i386 (Centos 6 32 bit) data from their server and currently only supports x64. This may be because Centos 6 is reaching its end of life (as of November 30 2020).

I am not familiar enough on how to replace this repository as it seems they have switched from using mirrors to a content distribution network (CDN) as of April 30, 2019. I also tried ‘yum update ius-release’ as the page suggests, but it made no difference.

To disable the repo.ius.io repository, do the following:

####show all files with ius in it:
ls -al |grep ius

-rw-r — r— 1 root root 669 May 1 12:00 ius-archive.repo
-rw-r — r— 1 root root 591 May 1 12:00 ius.repo

[Errno 14] HTTP/HTTPS Error 404

[Errno 14] PYCURL ERROR 22 — «The requested URL returned error: 403»

[Errno 14] Error 60 — It was impossible to connect to the CentOS servers

Summary

When trying to install or update packages using yum on client systems, yum is failing with one of the following errors:

[Errno 14] HTTP Error 404: Not Found

[Errno 14] HTTPS Error 404 - Not Found

[Errno 14] HTTP Error 404: Status 404

[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 403"

[Errno 14] Error 60 - It was impossible to connect to the CentOS servers

Leading Causes

1. You are not connected to the internet.

2. This issue can also occur if the system is able to communicate with given server but could not find or access the requested package or path on the server.

3. You have a misconfigured proxy server.

4. You have a local mirror with issues.

Fixes

1. Validate the system can see things on the internet.

2. This issue can also occur due to corruption of the local machine cache, try to clear cache on system:

yum clean all
rm -rf /var/cache/yum/*

3. If you have a proxy server, validate it is configured properly in /etc/yum.conf. Here is an example (your names, passwords, and port numbers will obviously be different).

proxy=http://mystuff.mydomain.com:1234
# Account details for yum connections
proxy_username=proxy-user
proxy_password=proxy-password

4. Temporarily comment out the mirror= line in the the .repo file, then:

yum clean all; yum makecache

If that does not work or if you still need help, try one of our community help platforms:

Forums | Mailing Lists | Other — Getting Help

Infopackets Reader Steve T. writes:

» Dear Dennis,

I am running Centos 6 32-bit (i386) on a virtual machine and recently I started having ‘PYCURL ERROR 22’ every time I use ‘yum list updates’ or ‘yum -y update’ to list and download updates. The error message says ‘[Errno 14] PYCURL ERROR 22 — The requested URL returned error: 404 Not Found‘. I have gone to the wiki.centos.org/yum-errors as the error message suggests, but have not been able to find a solution to this problem. Can you help? «

My response:

I asked Steve if he would like me to connect to his virtual machine using
my remote desktop support service in order to have a closer look at the problem, and he agreed. Below I will discuss my findings.

How to Fix: Yum [Errno 14] PYCURL ERROR 22 — 404 Not Found

As the centos.org wiki suggests, the first thing to do is to clear the yum cache as it may be corrupt, which will result in the PYCURL ERROR 22. To do so, open a terminal window / SSH and enter in the following:

yum clean all
rm -rf /var/cache/yum/*

If that does resolve your problem, please have a closer look at the error message. In Steve’s case it was the repo.ius.io mirror which was failing, as noted in the sample output below. In order to fix it, I went to the /etc/yum.repos.d directory and modified the ius.repo file in order to disable it.

Here is the sample output:

yum list updates

Loaded plugins: fastestmirror
Repository remi-safe is listed more than once in the configuration
Repository remi-php70 is listed more than once in the configuration
Loading mirror speeds from cached hostfile

* base: mirror.layeronline.com
* extras: mirror.layeronline.com
* remi: rpms.remirepo.net
* remi-php71: rpms.remirepo.net
* remi-safe: rpms.remirepo.net
* rpmforge: mirror.bacloud.com
* updates: mirror.layeronline.com

base | 3.7 kB 00:00
extras | 3.3 kB 00:00

https ://repo.ius.io/6/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 — «The requested URL returned error: 404 Not Found»

Trying other mirror.

To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

Disable Repository to Fix ‘PYCURL ERROR 22’

If you note the above output (red bold text), it lists the URL that is causing the error (repo.ius.io). To fix the error you need to disable the repository
via its configuration file, but this is really only a temporary fix to the issue
as it does not replace the broken repository.

For the record, I attempted to open https: //repo.ius.io/6/i386/repodata/repomd.xml via
the browser and it results in a 404 (file not found). After a bit more research,
it appears that repo.ius.io has removed all i386 (Centos 6 32 bit) data from their server and currently only supports x64. This may be because Centos 6 is reaching its end of life (as of November 30 2020).

I am not familiar enough on how to replace this repository as it seems
they have switched from using mirrors to a content distribution network
(CDN) as of April 30, 2019. I also tried ‘yum update ius-release’ as the
page suggests, but it made no difference.

To disable the repo.ius.io repository, do the following:

cd /etc/yum.repos.d

####show all files with ius in it:
ls -al |grep ius

-rw-r — r— 1 root root 669 May 1 12:00 ius-archive.repo
-rw-r — r— 1 root root 591 May 1 12:00 ius.repo                   
<=== this file
-rw-r — r— 1 root root 669 May 1 12:00 ius-testing.repo

####modify the repo file:
nano -w ius.repo

[ius]
name = IUS for Enterprise Linux 6 — $basearch
baseurl = https://repo.ius.io/6/$basearch/
####was enabled = 1, set to 0
enabled = 0
repo_gpgcheck = 0
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-IUS-6

That’s it! I hope that helps.

If anyone has any suggestions on getting the ius.repo to work again, please leave a comment below. For now, it appears to be taken offline — perhaps permanently.

Got a Computer Question or Problem? Ask Dennis!

I need more questions. If you have a computer question — or even a computer
problem that needs fixing — please
email me with your question so that I can write more articles like this one.
I can’t promise I’ll respond to all the messages I receive (depending on the
volume), but I’ll do my best.

About the author: Dennis Faas is the owner and operator of
Infopackets.com. With over 30 years of computing experience, Dennis’ areas of
expertise are a broad range and include PC hardware, Microsoft Windows, Linux,
network administration, and virtualization. Dennis holds a Bachelors degree in
Computer Science (1999) and has authored 6 books on the topics of MS Windows and
PC Security. If you like the advice you received on this page, please up-vote /
Like this page and share it with friends. For technical support inquiries,
Dennis can be reached via Live chat online this site using the Zopim Chat
service (currently located at the bottom left of the screen); optionally, you
can contact Dennis through the website
contact form.