Recently I did a yum update … and now it seems the last update has broke some links…
I’m getting message :
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:
-----end message —
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
I tried doing " yum clean all " to fix the problem link, not successful. Now It seems I’m not able to do any update … not sure how to fix the problem ? appreciate some suggestion
Thnx…I followed the last instruction…
If I do —> yum clean all --enablerepo=*; yum update --disablerepo=epel
It works and updated… after reboot … if I do – yum update — again problem still exist.
Only works if re-run the
yum clean all --enablerepo=*; yum update --disablerepo=epel
Not Sure what I have to change to fix the epel/x86_64. …
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
No, because this is not a good long-term solution. We should find out why epel doesn’t work. You may try to edit the .repo file, set baseurl and comment metalink, you may also try to change download.fedoraproject.org with another mirror:
You updated to centos 7.5 and are using the new kernel so ndpi module is not working. You may reboot with older kernel and it should work again. For information on the new updates, the problems and solutions see these threads:
As per your instruction, I commented out the metalink and use the baseurl … & ran --> yum update —> it works ok. No error message.
I then re-commented the baseurl and uncommented the metalink again …
then I ran —> yum clean all & sudo rm -rf /var/cache/yum & ran —> yum update again .
Now it seems to work. Although I have no update at this time but no ERROR Message.
Thanks a lot for the help, it seems for now … it’s working. Should I revert the kernel to older to fix the other DPI issure.
running 7.5.1804.
I noticed I stopped getting updates recently and a little googling led me here. Modifying the metalink data as suggested above does get yum update to work, however putting it back to original will just cause it to fail again. Yes I cleared the cache. The nethserver admin page shows my updates as “locked” trying to set it to “unlocked” results in the following error:
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
The install/update may have failed due to metadata caching issues. Please clean the cache by clicking the button below and retry the install/update operation.
Yes… I have the same error too after recently installed the 7.6Beta2. The updates work for 2 days then stopped…maybe the development team @dev_team can enlighten us here. Could be the repository is being updated with the final release being so close…
Unfortunately I’m still getting the same error. gui update fails, yum update fails.
If I comment out metalink and use base url my gui shows the update to 7.6.
Would there be any harm leaving it like that and doing the update? will update write a new epel.repo hopefully fixing the problem?
Yes…my command line update failed too… For the New Nethserver that I setup using the 7.6Beta., I was able to update using GUI but not from command line…
Another problem I’m having is in the Software Center - the Available and Installed pages are not showing any of the APPs available or installed…
I took a snapshot of my nethserver VM and tried to update to 7.6. There were a lot of errors and it got stuck in an update loop. I ended up restoring the snapshot. I also noticed an email domain in my allow email settings was marked as spam. Seems like my Nethserver install is committing suicide. I have had a couple unexpected shutdowns on the vm due to a defective UPS over the past 6 months so it’s possible something somewhere is corrupt.
Looks like a fresh install is in my future.
After a little more troubleshooting it looks like changing https to http in the
“metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-epel7&arch=$basearch” line allows yum update to run.
I don’t know much about repos but is it possible a repo either has an expired certificate or worse has been hijacked?
