On Friday 30 August 2019 04:54:14 Peter wrote:
>
> I would try this:
>
> yum clean all
ran okay.
> yum --disablerepo=epel update
ran okay but said there was nothing to update which I find hard to believe. It has been a month or so at least since the last successful update. It did complain about the REMI repos, which is odd as this all started when my yum update only updated PHP and Google Chrome, with PHP coming from REMI.
> yum --disablerepo=epel --enablerepo=extras reinstall epel-release
ran okay and successfully reinstalled epel-release.noarch 0:7-11
> yum update
Still failed in the same way as before. Full output below.
[root@stan2 ~]# yum clean all
Loaded plugins: fastestmirror, langpacks
Cleaning repos: base epel extras remi-php72 remi-safe updates
Cleaning up list of fastest mirrors
Other repos take up 57 k of disk space (use --verbose for details)
[root@stan2 ~]# yum --disablerepo=epel update
Loaded plugins: fastestmirror, langpacks
Determining fastest mirrors
* base: mirror.sov.uk.goscomb.net
* extras: mirror.clustered.net
* remi-php72: mirror.23media.com
* remi-safe: mirror.23media.com
* updates: mirrors.vooservers.com
base | 3.6 kB 00:00:00
extras | 3.4 kB 00:00:00
https://mirror.23media.com/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized."
Trying other mirror.
It was impossible to connect to the CentOS servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
or a transparent proxy that tampers with TLS security, or an incorrect system clock.
You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
https://mirror.oxilion.nl/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not trusted by the user."
Trying other mirror.
https://mirrors.ukfast.co.uk/sites/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized."
Trying other mirror.
remi-php72 | 3.0 kB 00:00:00
remi-safe | 3.0 kB 00:00:00
updates | 3.4 kB 00:00:00
(1/6): base/7/x86_64/group_gz | 166 kB 00:00:00
(2/6): extras/7/x86_64/primary_db | 215 kB 00:00:00
(3/6): remi-php72/primary_db | 225 kB 00:00:00
(4/6): remi-safe/primary_db | 1.6 MB 00:00:02
(5/6): updates/7/x86_64/primary_db | 7.4 MB 00:00:02
(6/6): base/7/x86_64/primary_db | 6.0 MB 00:00:03
No packages marked for update
[root@stan2 ~]# yum --disablerepo=epel --enablerepo=extras reinstall epel-release
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.sov.uk.goscomb.net
* extras: mirror.clustered.net
* remi-php72: mirror.23media.com
* remi-safe: mirror.23media.com
* updates: mirrors.vooservers.com
Resolving Dependencies
--> Running transaction check
---> Package epel-release.noarch 0:7-11 will be reinstalled
--> Finished Dependency Resolution
Dependencies Resolved
==============================================================================================================================================================
Package Arch Version Repository Size
==============================================================================================================================================================
Reinstalling:
epel-release noarch 7-11 extras 15 k
Transaction Summary
==============================================================================================================================================================
Reinstall 1 Package
Total download size: 15 k
Installed size: 24 k
Is this ok [y/d/N]: y
Downloading packages:
epel-release-7-11.noarch.rpm | 15 kB 00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Warning: RPMDB altered outside of yum.
Installing : epel-release-7-11.noarch 1/1
Verifying : epel-release-7-11.noarch 1/1
Installed:
epel-release.noarch 0:7-11
Complete!
[root@stan2 ~]# yum update
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
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
[root@stan2 ~]#
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
