epel-release

General support questions
Théo
Posts: 10
Joined: 2022/06/01 09:41:06

epel-release

Post by Théo » 2022/06/01 09:44:11

I have a problem it seems silly but I'm just a beginner (on Centos7):
After doing a:

Code: Select all

yum install epel-release
I get this when I want to do a yum update:

Code: Select all

[root@PLC7Cbis ~]# yum -y update
Modules complémentaires chargés : fastestmirror, langpacks
Repository updates is listed more than once in the configuration
Loading mirror speeds from cached hostfile


 One of the configured repositories failed (Inconnu),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

User avatar
TrevorH
Site Admin
Posts: 33218
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: epel-release

Post by TrevorH » 2022/06/01 10:17:34

Are you behind a firewall that restricts your access to the internet? Or do you need to use a web proxy to gain access? It would appear that your system is unable to contact the URL needed to allow EPEL to work.
Repository updates is listed more than once in the configuration
You might also want to fix this. You appear to have two entries in files in /etc/yum.repos.d/*.repo that define the [updates] repo. It should only be there once. I don't think it has anything to do with your EPEL error though.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Théo
Posts: 10
Joined: 2022/06/01 09:41:06

Re: epel-release

Post by Théo » 2022/06/01 10:21:49

Yes I am behind a firewall and I have this in /etc/yum.repos.d/:

Code: Select all

[root@PLC7Cbis yum.repos.d]# ls -ll
total 80
-rw-r--r-- 1 root root  151 24 mars  11:14 centos72.repo.old
-rw-r--r-- 1 root root  151 24 mars  11:14 centos79.repo
-rw-r--r-- 1 root root 1514  1 juin  10:55 centos7.repo
-rw-r--r-- 1 root root  233 24 mars  11:14 centos7-updates.repo
-rw-r--r-- 1 root root  185  1 juin  10:18 centos7-xtra.repo
-rw-r--r-- 1 root root  185 24 mars  11:14 centos7-xtra.repo.old
-rw-r--r-- 1 root root 1708  1 juin  10:16 CentOS-Base.repo
-rw-r--r-- 1 root root 1337  1 juin  10:16 CentOS-CR.repo
-rw-r--r-- 1 root root  670  1 juin  10:16 CentOS-Debuginfo.repo
-rw-r--r-- 1 root root  298  1 juin  10:16 CentOS-fasttrack.repo
-rw-r--r-- 1 root root  314 23 oct.   2020 CentOS-fasttrack.repo.rpmnew
-rw-r--r-- 1 root root  652  1 juin  10:16 CentOS-Media.repo
-rw-r--r-- 1 root root 1373  1 juin  10:16 CentOS-Sources.repo
-rw-r--r-- 1 root root 2027  1 juin  10:16 CentOS-Vault.repo
-rw-r--r-- 1 root root 8515 23 oct.   2020 CentOS-Vault.repo.rpmnew
-rw-r--r-- 1 root root  616 23 oct.   2020 CentOS-x86_64-kernel.repo
-rw-r--r-- 1 root root  951  2 oct.   2017 epel.repo
-rw-r--r-- 1 root root 1050  2 oct.   2017 epel-testing.repo
To bypass the firewall I modified the /etc/environment, created centos7.repo (national directory of my company) and I use:
curl --proxy-ntlm -U "CNAMTS/login:password" http://www.google.fr/

User avatar
TrevorH
Site Admin
Posts: 33218
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: epel-release

Post by TrevorH » 2022/06/01 11:16:14

You need to code the details of your proxy user/password in /etc/yum.conf, see man yum.conf and search for proxy for more details.
-rw-r--r-- 1 root root 151 24 mars 11:14 centos72.repo.old
-rw-r--r-- 1 root root 151 24 mars 11:14 centos79.repo
-rw-r--r-- 1 root root 1514 1 juin 10:55 centos7.repo
-rw-r--r-- 1 root root 233 24 mars 11:14 centos7-updates.repo
-rw-r--r-- 1 root root 185 1 juin 10:18 centos7-xtra.repo
-rw-r--r-- 1 root root 185 24 mars 11:14 centos7-xtra.repo.old
All of this lot look redudant from here (without being able to see their contents!), CentOS repos should be defined in CentOS-Base.repo already.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Théo
Posts: 10
Joined: 2022/06/01 09:41:06

Re: epel-release

Post by Théo » 2022/06/01 11:33:56

There is better with the configuration of yum.conf

I just have this at the end of the yum update:

Code: Select all

Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for base
perl-LWP-Protocol-https-6.04-4 FAILED
http://yum-rn.cnamts.fr/centos/7/base/Packages/perl-LWP-Protocol-https-6.04-4.el7.noarch.rpm: [Errno 14] HTTP Error 403 - Forbidden   ]  0.0 B/s |    0 B  --:--:-- ETA
Essai d'un autre miroir.
perl-Crypt-DES-2.05-20.el7.x86 FAILED
http://yum-rn.cnamts.fr/centos/7/base/Packages/perl-Crypt-DES-2.05-20.el7.x86_64.rpm: [Errno 14] HTTP Error 403 - Forbidden           ]  0.0 B/s |    0 B  --:--:-- ETA
Essai d'un autre miroir.

Error downloading packages:
  perl-LWP-Protocol-https-6.04-4.el7.noarch: [Errno 256] No more mirrors to try.
  perl-Crypt-DES-2.05-20.el7.x86_64: [Errno 256] No more mirrors to try.

Théo
Posts: 10
Joined: 2022/06/01 09:41:06

Re: epel-release

Post by Théo » 2022/06/01 11:41:02

Code: Select all

[root@PLC7Cbis yum.repos.d]# yum repolist
Modules complémentaires chargés : fastestmirror, langpacks
Repository updates is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * epel: epel.mirror.far.fi
http://yum-rn.cnamts.fr/centos/7/base/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Essai d'un autre miroir.
To address this issue please refer to the below wiki article

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

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

http://yum-rn.cnamts.fr/centos/7/centos-sclo-rh/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Essai d'un autre miroir.
http://yum-rn.cnamts.fr/centos/7/centos-sclo-sclo/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Essai d'un autre miroir.
http://yum.cnamts.fr/centos/7/7.9/x86_64/Server/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Essai d'un autre miroir.
http://yum-rn.cnamts.fr/centos/7/extras/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Essai d'un autre miroir.
http://yum.cnamts.fr/centos/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Essai d'un autre miroir.
id du dépôt                                                       nom du dépôt                                                                                    statut
base                                                              CentOS-7 - Base                                                                                 10 072
centos-sclo-rh                                                    CentOS-7 - SCLo rh                                                                              14 248
centos-sclo-sclo                                                  CentOS-7 - SCLo sclo                                                                             1 585
centos79/x86_64                                                   centos79                                                                                        10 072
epel/x86_64                                                       Extra Packages for Enterprise Linux 7 - x86_64                                                  13 753
extras                                                            CentOS-7 - Extras                                                                                  512
updates/x86_64                                                    centos 7 - x86_64 - UPDATES                                                                         51
repolist: 50 293

Théo
Posts: 10
Joined: 2022/06/01 09:41:06

Re: epel-release

Post by Théo » 2022/06/01 11:44:25

All lines in CentOS-Base.repo are commented out and in the centos7.repo I have the same lines but uncommented with company repos :

Code: Select all

# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-7 - Base
baseurl=http://yum-rn.cnamts.fr/centos/7/base/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#released updates
[updates]
name=CentOS-7 - Updates
baseurl=http://yum-rn.cnamts.fr/centos/7/updates/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that may be useful
[extras]
name=CentOS-7 - Extras
baseurl=http://yum-rn.cnamts.fr/centos/7/extras/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

[centos-sclo-sclo]
name=CentOS-$releasever - SCLo sclo
baseurl=http://yum-rn.cnamts.fr/centos/7/centos-sclo-sclo
gpgcheck=0
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-SCLo

[centos-sclo-rh]
name=CentOS-$releasever - SCLo rh
baseurl=http://yum-rn.cnamts.fr/centos/7/centos-sclo-rh/
gpgcheck=0
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-SCLo


#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-7 - Plus
baseurl=http://yum-rn.cnamts.fr/centos/7/centosplus/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

Théo
Posts: 10
Joined: 2022/06/01 09:41:06

Re: epel-release

Post by Théo » 2022/06/01 11:53:33

Wait I may have a solution.

User avatar
jlehtone
Posts: 4530
Joined: 2007/12/11 08:17:33
Location: Finland

Re: epel-release

Post by jlehtone » 2022/06/01 11:54:42

HTTP Error 403 - Forbidden
The HTTP server yum-rn.cnamts.fr does not want you to access those files.

Should you be able to browse, say http://yum-rn.cnamts.fr/centos/7/extras/ directly or via a proxy?

Théo
Posts: 10
Joined: 2022/06/01 09:41:06

Re: epel-release

Post by Théo » 2022/06/01 12:17:14

I'm thinking with a proxy but I think I've configured it well though.

And when I want to install it with myself (it's in french if you want to translate):

Code: Select all

[root@PLC7Cbis ~]# rpm -Uvh perl-Crypt-DES-2.05-20.el7.src.rpm perl-LWP-Protocol-https-6.04-4.el7.src.rpm
Mise à jour / installation...
   1:perl-Crypt-DES-2.05-20.el7       ################################# [100%]
attention : utilisateur mockbuild inexistant - utilisation de root
attention : groupe mockbuild inexistant - utilisation de root
attention : utilisateur mockbuild inexistant - utilisation de root
attention : groupe mockbuild inexistant - utilisation de root
   2:perl-LWP-Protocol-https-6.04-4.el################################# [100%]
attention : utilisateur mockbuild inexistant - utilisation de root
attention : groupe mockbuild inexistant - utilisation de root
attention : utilisateur mockbuild inexistant - utilisation de root
attention : groupe mockbuild inexistant - utilisation de root

Post Reply