yum appears to be unstable.
Hi guys, I'm still using old CentOS7.9 and cPanel 110.0.36.
I have two errors:
The system cannot check the kernel status: “/usr/bin/yum” reported error code “1” when it ended: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known" Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known" 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= ... 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 or subscription-manager repos --disable= 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=.skip_if_unavailable=true Cannot find a valid baseurl for repo: extras/7/x86_64
and
Failed to check whether active services are up-to-date: “/usr/local/cpanel/bin/needs-restarting-cpanel” reported error code “1” when it ended: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known" failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. http://asi-fs-n.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
I was planning on elevate to Almalinux but gotta fix this first.
Any idea on how to fix this would be greatly appreciated?
Thank you
-
Here is the log:
System update process has started. “/usr/bin/yum” reported error code “1” when it ended: w/ /usr/bin/yum upgrade -y Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known" Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known" 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 find a valid baseurl for repo: extras/7/x86_64 Often errors like this can be resolved by running `yum makecache` System update process has finished.
0 -
Official support article:
The next issue you'll likely encounter is:
https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
...TuxCare (CloudLinux Network) is who cPanel partnered with for their ELS program and July is supposed to be free with a monthly adder going to your license to keep it going:
https://cpanel.net/blog/announcements/extended-lifecycle-support-oses-update/
However, I presume that either things are still in motion, licensing wise, or, CLN is just unable to handle the in rush.
Hoping to see things clear up today.1 -
Thank you for this, would you agree that I can ignore the errors for a little while if I'm planning to change server and import all cpanel accounts?
0 -
I don't believe you'll run into issues if you ignore them outside of receiving errors from cPanel to your Contact Address setup in WHM (depending on how your Contact Manager is setup in WHM) and, of course, YUM not functioning (which CAN bring other challenges)
If nothing else, you could run the repair scripts to get the CentOS base repo tidied up and then simply allow the ELS repo to heal (hopefully someone from cPanel will chime in on this)
1
Please sign in to leave a comment.
Comments
4 comments