Page 1 of 1

3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 15:18
by stevis
I'm trying to perform the upgrade fro 3.0.0.9 from 3.0.0.8 and got through the first pass of the update which updated the kernel, and now, after rebooting, I get this every time I try to complete the update:

Starting update to E.F.A. 3.0.0.9
[EFA] Good you are root
Beginning System Backup at 03222016 090014
Backup Completed at 03222016 090017
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
cp: omitting directory `/tmp/EFA-Staging/Scripts/lib-EFA-Configure/new'
Loaded plugins: fastestmirror, security
Cleaning repos: EFA base epel extras updates
Cleaning up Everything
Cleaning up list of fastest mirrors
Loaded plugins: fastestmirror, security
Setting up Update Process
Determining fastest mirrors
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Could not retrieve mirrorlist https://dl.efa-project.org/rpm/mirrors-efa error was
14: Peer cert cannot be verified or peer cert invalid

Update to Version 3.0.0.9 FAILED. Updates cancelled.
Please visit http://www.efa-project.org for more information.
sendmail: fatal: root(0): No recipient addresses found in message header
All done
Please restart your system as soon as possible.
If your system does not return to a command prompt
you can now safely press ctrl-c to abort logsave
Thank you for using E.F.A.

Any thoughts or suggestions?

Thanks,

Steve

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 15:36
by shawniverson
Try this first:

Code: Select all

sudo yum --disablerepo=epel update ca-certificates
sudo yum --enablerepo=epel clean all

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 16:02
by stevis
Changed the errors a bit, but still no luck.

Starting update to E.F.A. 3.0.0.9
[EFA] Good you are root
Beginning System Backup at 03222016 100140
Backup Completed at 03222016 100141
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
cp: omitting directory `/tmp/EFA-Staging/Scripts/lib-EFA-Configure/new'
error: package perl-Convert-TNEF is not installed
error: package perl-IO-Multiplex is not installed
error: package perl-Net-Server is not installed
error: package re2c is not installed
error: package unrar is not installed
error: package perl-IP-Country is not installed
error: package perl-Mail-SPF-Query is not installed
error: package perl-Net-Ident is not installed
error: package perl-Mail-ClamAV is not installed
error: package rpmforge-release is not installed
cp: cannot create regular file `/etc/yum.repos.d/EFA.repo': Permission denied
Loaded plugins: fastestmirror, security
Cleaning repos: EFA base epel extras updates
Cleaning up Everything
Cleaning up list of fastest mirrors
Loaded plugins: fastestmirror, security
Setting up Update Process
Determining fastest mirrors
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Update to Version 3.0.0.9 FAILED. Updates cancelled.
Please visit http://www.efa-project.org for more information.
sendmail: fatal: root(0): No recipient addresses found in message header
All done
Please restart your system as soon as possible.
If your system does not return to a command prompt
you can now safely press ctrl-c to abort logsave
Thank you for using E.F.A.

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 16:07
by shawniverson
That is actually a little better....no ssl error now. You can ignore the package not installed errors (already removed from first attempt)

Some reason you can't download the metalink...

What do you get when you do this?

Code: Select all

 wget -O test.xml https://mirrors.fedoraproject.org/metalink?repo=epel-6
Does test.xml look like this?

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Tue, 22 Mar 2016 16:06:28 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">
<!--
# either path=, or repo= and arch= must be specified
-->
</metalink>

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 16:09
by stevis
I get this:

$ wget -O test.xml https://mirrors.fedoraproject.org/metalink?repo=epel-6
--2016-03-22 10:08:04-- https://mirrors.fedoraproject.org/metalink?repo=epel-6
Resolving mirrors.fedoraproject.org... 140.211.169.196, 209.132.181.15, 67.203.2.67, ...
Connecting to mirrors.fedoraproject.org|140.211.169.196|:443... connected.
ERROR: cannot verify mirrors.fedoraproject.orgâs certificate, issued by â/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CAâ
Unable to locally verify the issuerâs authority.
To connect to mirrors.fedoraproject.org insecurely, use â--no-check-certificateâ.

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 16:12
by shawniverson
To work around this, try adding "sslverify=false" to /etc/yum.conf, update, then remove this setting.

This is less secure, but may allow you to update.

Something is wrong with your SSL/CA certificate verification. Hopefully the update process fixes something along the way, but if not, I would encourage you to spend some time and try to isolate that problem.

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 16:17
by stevis
Looks like I may have borked my copy of ca-bundle.crt when I installed my SSL cert a few weeks ago...luckily, I kept a copy of the original. Putting it back in place seems to have fixed the issue (update running right now). Now I just have to see if my SSL works after the upgrade finishes.

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 22 Mar 2016 17:00
by stevis
Yup, that fixed it. Thanks for all of your help!

Re: 3.0.0.9 Upgrade - Cannot retrieve metalink for repository: epel

Posted: 03 Apr 2016 16:23
by ashweb
I had the same issue as this thread, however my machine could not resolve mirrors.fedoraproject.org so I set a static entry in /etc/hosts to get it to update.

My system has not problem resolving any other name.