Varnish repo failed

pamamolf · Sep 6, 2017

It is temporary

Now i just run:

yum clean all and the yum update and i got again duplicates:

varnishcache_varnish41/x86_64/signature | 836 B 00:00:00
varnishcache_varnish41/x86_64/signature | 1.0 kB 00:00:00 !!!
varnishcache_varnish41-source/signature | 836 B 00:00:00
varnishcache_varnish41-source/signature | 1.0 kB 00:00:00 !!!
(1/9): base/7/x86_64/group_gz | 155 kB 00:00:00
Click to expand...

the rest related entries are:

(1/3): varnishcache_varnish41/x86_64/primary | 9.8 kB 00:00:00
(2/3): varnishcache_varnish41-source/primary | 2.2 kB 00:00:00
Click to expand...

varnishcache_varnish41 43/43
varnishcache_varnish41-source 13/13
Click to expand...

pamamolf · Sep 6, 2017

Looks like there is a duplicate signature and the rest x86_64 and source are normal?

Maybe that info help?
Code:
https://packagecloud.io/app/varnishcache/varnish41/gpg
Don't know why we have that issue

eva2000 · Sep 6, 2017

not sure why either though should be fine to leave it as is
Code (Text):
ls -lahR /var/lib/yum/repos/x86_64/7/varnishcache_varnish41/gpgdir
/var/lib/yum/repos/x86_64/7/varnishcache_varnish41/gpgdir:
total 20K
drwxr-xr-x 2 root root 4.0K Sep  6 00:04 .
drwxr-xr-x 4 root root 4.0K Sep  5 04:39 ..
-rw-r--r-- 1 root root    0 Sep  5 04:39 gpg.conf
-rw------- 1 root root 2.8K Sep  5 04:39 pubring.gpg
-rw------- 1 root root 2.8K Sep  5 04:39 pubring.gpg~
-rw------- 1 root root    0 Sep  5 04:39 secring.gpg
-rw------- 1 root root 1.3K Sep  5 04:39 trustdb.gpg
Code (Text):
ls -lahR /var/lib/yum/repos/x86_64/7/varnishcache_varnish41/gpgdir-ro/
/var/lib/yum/repos/x86_64/7/varnishcache_varnish41/gpgdir-ro/:
total 20K
drwxr-xr-x 2 root root 4.0K Sep  5 04:39 .
drwxr-xr-x 4 root root 4.0K Sep  5 04:39 ..
-rwxr-xr-x 1 root root  138 Sep  5 04:39 gpg.conf
-rwxr-xr-x 1 root root 2.8K Sep  5 04:39 pubring.gpg
-rwxr-xr-x 1 root root    0 Sep  5 04:39 pubring.gpg~
-rwxr-xr-x 1 root root    0 Sep  5 04:39 secring.gpg
-rwxr-xr-x 1 root root 1.3K Sep  5 04:39 trustdb.gpg
but might be by design gpgdir-ro is read only version for non-root users I am guessing from discussion here.

when importing a gpgkey - write out a -ro version of the gpgdir for non-root users to use also setup the difficult-to-grok gpgoptions necessary to make a readonly GNUPGHOME work with a simple key validation
Click to expand...

and yum/ChangeLog at master · rpm-software-management/yum · GitHub

* yum/misc.py: when importing a gpgkey - write out a -ro version of
the gpgdir for non-root users to use also setup the
difficult-to-grok gpgoptions necessary to make a readonly GNUPGHOME
work with a simple key validation change setCacheDir() so it can
take an alternative prefix and so we don't set a prefix then assume
something else entirely
Click to expand...

pamamolf · Sep 6, 2017

If it will not cause any issues on updates then is fine

pamamolf · Sep 6, 2017

After the above updates how can i totally disable that repo as i do not use Varnish?

eva2000 · Sep 6, 2017

edit .repo file to set enable=0 or use like previously
Code (Text):
yum-config-manager --disable varnishcache_varnish41

pamamolf · Sep 6, 2017

I just got this one:

One of the configured repositories failed (Unknown),
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
Click to expand...

Don't know why as i have already apply the update to Centminmod and re run it....

total 172K
drwxr-xr-x. 2 root root 4.0K Sep 6 11:04 .
drwxr-xr-x. 93 root root 12K Sep 6 11:04 ..
-rw-r--r-- 1 root root 1.8K Dec 14 2016 CentOS-Base.OLD
-rw-r--r--. 1 root root 1.8K Dec 14 2016 CentOS-Base.repo
-rw-r--r-- 1 root root 1.3K Feb 23 2016 CentOS-CR.OLD
-rw-r--r--. 1 root root 1.3K Feb 23 2016 CentOS-CR.repo
-rw-r--r-- 1 root root 649 Nov 29 2016 CentOS-Debuginfo.repo
-rw-r--r-- 1 root root 314 Nov 29 2016 CentOS-fasttrack.repo
-rw-r--r-- 1 root root 630 Nov 29 2016 CentOS-Media.repo
-rw-r--r-- 1 root root 1.3K Nov 29 2016 CentOS-Sources.repo
-rw-r--r-- 1 root root 2.9K Nov 29 2016 CentOS-Vault.repo
-rw-r--r-- 1 root root 1.1K Nov 9 2016 city-fan.org.OLD
-rw-r--r-- 1 root root 1.2K Jun 11 00:59 city-fan.org.repo
-rw-r--r-- 1 root root 1.1K Apr 8 21:35 epel.OLD
-rw-r--r-- 1 root root 1.1K Jul 22 20:53 epel.repo
-rw-r--r-- 1 root root 951 Jun 24 15:04 epel.repo.rpmnew
-rw-r--r-- 1 root root 1.1K Jun 24 15:04 epel-testing.repo
-rw-r--r-- 1 root root 169 Feb 23 2016 mariadb.repo
-rw-r--r-- 1 root root 693 Jul 1 22:01 mirrors-rpmforge
-rw-r--r-- 1 root root 673 Jul 1 22:01 mirrors-rpmforge-extras
-rw-r--r-- 1 root root 673 Jul 1 21:32 mirrors-rpmforge-extras.rpmsave
-rw-r--r-- 1 root root 693 Jul 1 21:32 mirrors-rpmforge.rpmsave
-rw-r--r-- 1 root root 683 Jul 1 22:01 mirrors-rpmforge-testing
-rw-r--r-- 1 root root 683 Jul 1 21:32 mirrors-rpmforge-testing.rpmsave
-rw-r--r-- 1 root root 202 Oct 30 2010 newrelic.repo
-rw-r--r-- 1 root root 2.5K Sep 22 2014 percona-release.OLD
-rw-r--r-- 1 root root 2.6K Feb 23 2016 percona-release.repo
-rw-r--r-- 1 root root 2.3K Dec 9 2015 remi.OLD
-rw-r--r-- 1 root root 457 Jun 30 12:15 remi-php54.repo
-rw-r--r-- 1 root root 1.3K Jun 30 12:15 remi-php70.repo
-rw-r--r-- 1 root root 1.3K Jun 30 12:15 remi-php71.repo
-rw-r--r-- 1 root root 1.3K Jun 30 12:15 remi-php72.repo
-rw-r--r-- 1 root root 2.4K Feb 23 2016 remi.repo
-rw-r--r-- 1 root root 2.6K Feb 10 2017 remi.repo.rpmnew
-rw-r--r-- 1 root root 449 Sep 6 11:04 remi-safe.repo
-rw-r--r-- 1 root root 751 Feb 10 2017 remi-safe.repo.rpmnew
-rw-r--r-- 1 root root 1.2K Jun 12 2014 rpmforge.OLD
-rw-r--r-- 1 root root 1.2K Jul 1 22:01 rpmforge.repo
-rw-r--r-- 1 root root 603 Sep 6 11:02 varnishcache_varnish41.repo
-rw-r--r-- 1 root root 212 Jul 9 2013 varnish.OLD
-rw-r--r-- 1 root root 223 Feb 23 2016 varnish.repo.rpmsave
Click to expand...

pamamolf · Sep 6, 2017

Checking around it seems like an issue with the https certificates that need a renew or the mirrors have some issues....A few suggest to use base url instead for the:

/etc/yum.repos.d/epel.repo
Click to expand...

I found also some info related to update the nss packages...

Any ideas ?

Thank you

pamamolf · Sep 6, 2017

Centos 7

My epel.repo

[epel]
name=Extra Packages for Enterprise Linux 7 - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch
failovermethod=priority
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
priority=3
exclude=varnish varnish-libs clamd clamav clamav-db galera nodejs clamav-devel nginx mongodb* scl-utils

[epel-debuginfo]
name=Extra Packages for Enterprise Linux 7 - $basearch - Debug
#baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch/debug
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1

[epel-source]
name=Extra Packages for Enterprise Linux 7 - $basearch - Source
#baseurl=http://download.fedoraproject.org/pub/epel/7/SRPMS
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-source-7&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1
Click to expand...

eva2000 · Sep 6, 2017

Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
Click to expand...

<repoid> is an invalid repo name, so one of your .repo files has an incorrect reference
Code (Text):
grep -r repoid /etc/yum.repos.d/

pamamolf · Sep 6, 2017

grep -r repoid /etc/yum.repos.d/
Click to expand...

returns nothing.....

It sounds like repos have Id's and we can use ID instead of name to disable it.....doesn't seem to be related to a repo name "repoid" or not?

pamamolf · Sep 6, 2017

The issue is 100% with the epel.repo as if i run this:

yum --disablerepo=epel -y update ca-certificates
Click to expand...

I don't get any errors but after that running again yum update without disabling the epel repo the same error is coming up

eva2000 · Sep 6, 2017

could be broken epel mirror, from previous post your epel mirror was = mirror.csclub.uwaterloo.ca so you can try excluding that from fast mirror plugin /etc/yum/pluginconf.d/fastestmirror.conf + do yum clean all

Code (Text):

yum repolist all
Loaded plugins: fastestmirror, priorities, versionlock
base | 3.6 kB 00:00:00
epel/x86_64/metalink | 13 kB 00:00:00
epel | 4.3 kB 00:00:00
extras | 3.4 kB 00:00:00
mariadb | 2.9 kB 00:00:00
nodesource | 2.5 kB 00:00:00
rpmforge | 1.9 kB 00:00:00
updates | 3.4 kB 00:00:00
varnishcache_varnish41/x86_64/signature | 836 B 00:00:00
varnishcache_varnish41/x86_64/signature | 1.0 kB 00:00:00 !!!
varnishcache_varnish41-source/signature | 836 B 00:00:00
varnishcache_varnish41-source/signature | 1.0 kB 00:00:00 !!!
(1/9): base/7/x86_64/group_gz | 155 kB 00:00:00
(2/9): base/7/x86_64/primary_db | 5.6 MB 00:00:00
(3/9): epel/x86_64/group_gz | 170 kB 00:00:00
(4/9): epel/x86_64/updateinfo | 817 kB 00:00:00
(5/9): mariadb/primary_db | 19 kB 00:00:00
(6/9): extras/7/x86_64/primary_db | 191 kB 00:00:00
(7/9): updates/7/x86_64/primary_db | 7.8 MB 00:00:03
(8/9): epel/x86_64/primary_db | 4.8 MB 00:00:03
(9/9): nodesource/x86_64/primary_db | 60 kB 00:00:04
(1/3): varnishcache_varnish41/x86_64/primary | 9.8 kB 00:00:00
(2/3): varnishcache_varnish41-source/primary | 2.2 kB 00:00:00
(3/3): rpmforge/primary_db | 125 kB 00:00:00
Determining fastest mirrors
* base: centos.bhs.mirrors.ovh.net
* epel: mirror.csclub.uwaterloo.ca

pamamolf · Sep 6, 2017

I have that issue on two servers and maybe the previous post was from the first server.....

I am not able to run yum repolist all as i am getting:

yum repolist all
Loaded plugins: fastestmirror, priorities, versionlock

One of the configured repositories failed (Unknown),
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
Click to expand...

I also try:

yum --disablerepo=epel -y update nss
yum --disablerepo=epel -y update ca-certificates
Click to expand...

No updates for both as i update the servers every x days.....

I also try the base url and change the https to http for mirrors but nothing

Don't know how to remove/exclude a specific mirror or even check what mirror is in use or have the issue

eva2000 · Sep 6, 2017

in /etc/yum/pluginconf.d/fastestmirror.conf uncomment exclude= and add mirror urls you want to exclude i.e. mirror.csclub.uwaterloo.ca
Code (Text):
[main]
enabled=1
verbose=0
always_print_best_host = true
socket_timeout=3
#  Relative paths are relative to the cachedir (and so works for users as well
# as root).
hostfilepath=timedhosts.txt
maxhostfileage=10
maxthreads=15
#exclude=.gov, facebook
#include_only=.nl,.de,.uk,.ie

pamamolf · Sep 6, 2017

Ok i did it but didn't work

Any ideas on how can check which mirror is failing every time so i can exclude it?

Sunka · Sep 6, 2017

Code (Text):

[root@upcloud ~]# yum repolist all
Loaded plugins: fastestmirror, priorities, versionlock
Loading mirror speeds from cached hostfile
 * base: ftp.hosteurope.de
 * epel: mirror.23media.de
 * extras: ftp.hosteurope.de
 * updates: ftp.hosteurope.de
129 packages excluded due to repository priority protections
repo id                              repo name                                             status
C7.0.1406-base/x86_64                CentOS-7.0.1406 - Base                                disabled
C7.0.1406-centosplus/x86_64          CentOS-7.0.1406 - CentOSPlus                          disabled
C7.0.1406-extras/x86_64              CentOS-7.0.1406 - Extras                              disabled
C7.0.1406-fasttrack/x86_64           CentOS-7.0.1406 - CentOSPlus                          disabled
C7.0.1406-updates/x86_64             CentOS-7.0.1406 - Updates                             disabled
C7.1.1503-base/x86_64                CentOS-7.1.1503 - Base                                disabled
C7.1.1503-centosplus/x86_64          CentOS-7.1.1503 - CentOSPlus                          disabled
C7.1.1503-extras/x86_64              CentOS-7.1.1503 - Extras                              disabled
C7.1.1503-fasttrack/x86_64           CentOS-7.1.1503 - CentOSPlus                          disabled
C7.1.1503-updates/x86_64             CentOS-7.1.1503 - Updates                             disabled
C7.2.1511-base/x86_64                CentOS-7.2.1511 - Base                                disabled
C7.2.1511-centosplus/x86_64          CentOS-7.2.1511 - CentOSPlus                          disabled
C7.2.1511-extras/x86_64              CentOS-7.2.1511 - Extras                              disabled
C7.2.1511-fasttrack/x86_64           CentOS-7.2.1511 - CentOSPlus                          disabled
C7.2.1511-updates/x86_64             CentOS-7.2.1511 - Updates                             disabled
base/7/x86_64                        CentOS-7 - Base                                       enabled: 7,261+2,102
base-debuginfo/x86_64                CentOS-7 - Debuginfo                                  disabled
base-source/7                        CentOS-7 - Base Sources                               disabled
c7-media                             CentOS-7 - Media                                      disabled
centos-sclo-rh/x86_64                CentOS-7 - SCLo rh                                    enabled:   5,851+151
centos-sclo-rh-debuginfo/x86_64      CentOS-7 - SCLo rh Debuginfo                          disabled
centos-sclo-rh-source                CentOS-7 - SCLo rh Sources                            disabled
centos-sclo-rh-testing/x86_64        CentOS-7 - SCLo rh Testing                            disabled
centos-sclo-sclo/x86_64              CentOS-7 - SCLo sclo                                  enabled:         467
centos-sclo-sclo-debuginfo/x86_64    CentOS-7 - SCLo sclo Debuginfo                        disabled
centos-sclo-sclo-source              CentOS-7 - SCLo sclo Sources                          disabled
centos-sclo-sclo-testing/x86_64      CentOS-7 - SCLo sclo Testing                          disabled
centosplus/7/x86_64                  CentOS-7 - Plus                                       disabled
centosplus-source/7                  CentOS-7 - Plus Sources                               disabled
city-fan.org/7                       city-fan.org repository for Red Hat Enterprise Linux  disabled
city-fan.org-debuginfo/7             city-fan.org debuginfo repository for Red Hat Enterpr disabled
city-fan.org-source/7                city-fan.org source repository for Red Hat Enterprise disabled
cr/7/x86_64                          CentOS-7 - cr                                         disabled
elasticsearch-5.x                    Elasticsearch repository for 5.x packages             enabled:      128+90
epel/x86_64                          Extra Packages for Enterprise Linux 7 - x86_64        enabled:  10,990+892
epel-debuginfo/x86_64                Extra Packages for Enterprise Linux 7 - x86_64 - Debu disabled
epel-source/x86_64                   Extra Packages for Enterprise Linux 7 - x86_64 - Sour disabled
epel-testing/x86_64                  Extra Packages for Enterprise Linux 7 - Testing - x86 disabled
epel-testing-debuginfo/x86_64        Extra Packages for Enterprise Linux 7 - Testing - x86 disabled
epel-testing-source/x86_64           Extra Packages for Enterprise Linux 7 - Testing - x86 disabled
extras/7/x86_64                      CentOS-7 - Extras                                     enabled:       449+2
extras-source/7                      CentOS-7 - Extras Sources                             disabled
fasttrack/7/x86_64                   CentOS-7 - fasttrack                                  disabled
mariadb                              MariaDB                                               enabled:        14+2
percona-experimental-noarch/7        Percona-Experimental YUM repository - noarch          disabled
percona-experimental-source/7        Percona-Experimental YUM repository - Source packages disabled
percona-experimental-x86_64/7/x86_64 Percona-Experimental YUM repository - x86_64          disabled
percona-release-noarch/7             Percona-Release YUM repository - noarch               disabled
percona-release-source/7             Percona-Release YUM repository - Source packages      disabled
percona-release-x86_64/7/x86_64      Percona-Release YUM repository - x86_64               disabled
percona-testing-noarch/7             Percona-Testing YUM repository - noarch               disabled
percona-testing-source/7             Percona-Testing YUM repository - Source packages      disabled
percona-testing-x86_64/7/x86_64      Percona-Testing YUM repository - x86_64               disabled
remi                                 Remi's RPM repository for Enterprise Linux 7 - x86_64 disabled
remi-debuginfo/x86_64                Remi's RPM repository for Enterprise Linux 7 - x86_64 disabled
remi-php54                           Remi's PHP 5.4 RPM repository for Enterprise Linux 7  disabled
remi-php55                           Remi's PHP 5.5 RPM repository for Enterprise Linux 7  disabled
remi-php55-debuginfo/x86_64          Remi's PHP 5.5 RPM repository for Enterprise Linux 7  disabled
remi-php56                           Remi's PHP 5.6 RPM repository for Enterprise Linux 7  disabled
remi-php56-debuginfo/x86_64          Remi's PHP 5.6 RPM repository for Enterprise Linux 7  disabled
remi-php70                           Remi's PHP 7.0 RPM repository for Enterprise Linux 7  disabled
remi-php70-debuginfo/x86_64          Remi's PHP 7.0 RPM repository for Enterprise Linux 7  disabled
remi-php70-test                      Remi's PHP 7.0 test RPM repository for Enterprise Lin disabled
remi-php70-test-debuginfo/x86_64     Remi's PHP 7.0 test RPM repository for Enterprise Lin disabled
remi-php71                           Remi's PHP 7.1 RPM repository for Enterprise Linux 7  disabled
remi-php71-debuginfo/x86_64          Remi's PHP 7.1 RPM repository for Enterprise Linux 7  disabled
remi-php71-test                      Remi's PHP 7.1 test RPM repository for Enterprise Lin disabled
remi-php71-test-debuginfo/x86_64     Remi's PHP 7.1 test RPM repository for Enterprise Lin disabled
remi-php72                           Remi's PHP 7.2 RPM repository for Enterprise Linux 7  disabled
remi-php72-debuginfo/x86_64          Remi's PHP 7.2 RPM repository for Enterprise Linux 7  disabled
remi-php72-test                      Remi's PHP 7.2 test RPM repository for Enterprise Lin disabled
remi-php72-test-debuginfo/x86_64     Remi's PHP 7.2 test RPM repository for Enterprise Lin disabled
remi-safe                            Safe Remi's RPM repository for Enterprise Linux 7 - x disabled
remi-test                            Remi's test RPM repository for Enterprise Linux 7 - x disabled
remi-test-debuginfo/x86_64           Remi's test RPM repository for Enterprise Linux 7 - x disabled
updates/7/x86_64                     CentOS-7 - Updates                                    enabled:   1,769+377
updates-source/7                     CentOS-7 - Updates Sources                            disabled
!varnishcache_varnish41/x86_64       varnishcache_varnish41                                enabled:       33+10
!varnishcache_varnish41-source       varnishcache_varnish41-source                         enabled:           0
repolist: 26,962

pamamolf · Sep 6, 2017

I can see on your output the link but it's not the same for me:

yum repolist all
Loaded plugins: fastestmirror, priorities, versionlock
base | 3.6 kB 00:00:00
digitalocean-agent | 3.3 kB 00:00:00
base/7/x86_64/primary_db | 5.6 MB 00:00:00
digitalocean-agent/x86_64/primary_db | 1.7 kB 00:00:00
extras/7/x86_64 | 3.4 kB 00:00:00
extras/7/x86_64/primary_db | 191 kB 00:00:00
mariadb | 2.9 kB 00:00:00
mariadb/primary_db | 19 kB 00:00:00
rpmforge | 1.9 kB 00:00:00
rpmforge/primary_db | 125 kB 00:00:00
updates/7/x86_64 | 3.4 kB 00:00:00
updates/7/x86_64/primary_db | 7.8 MB 00:00:00

One of the configured repositories failed (Unknown),
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
Click to expand...

eva2000 · Sep 6, 2017

pamamolf said: ↑

Ok i did it but didn't work

Any ideas on how can check which mirror is failing every time so i can exclude it?
Click to expand...

try running yum repolist all command in verbose mode

pamamolf · Sep 6, 2017

Not sure that -v is enabling verbose but i got this:

yum -v repolist all
Loading "fastestmirror" plugin
Loading "priorities" plugin
Loading "versionlock" plugin
Config time: 0.015
Yum version: 3.4.3
base | 3.6 kB 00:00:00
digitalocean-agent | 3.3 kB 00:00:00

One of the configured repositories failed (Unknown),
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
Click to expand...

Log in / Register

Forums

Learn about Centmin Mod LEMP Stack today

Varnish repo failed

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

Sunka Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

.

Log in / Register

Useful Searches

Learn about Centmin Mod LEMP Stack today

Varnish repo failed

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

Sunka Well-Known Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

.