Elevate to AlmaLinux 8
Answered
Hello, how can I fix these errors? I am a beginner, but I need to migrate my server. Thank you.
[root@vmi724241 ~]# /scripts/elevate-cpanel --check
* 2024-07-13 13:19:51 [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading.
* 2024-07-13 13:19:51 [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-13 13:19:51 [INFO] Running: /usr/bin/yum list extras
* 2024-07-13 13:19:51 [INFO]
* 2024-07-13 13:19:54 [INFO]
* 2024-07-13 13:19:57 [WARN] Initial run of "yum makecache" failed: http://asi-fs-l.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
One of the configured repositories failed (CentOS-7-Base),
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=base ...
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 base
or
subscription-manager repos --disable=base
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=base.skip_if_unavailable=true
failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-l.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-13 13:19:57 [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-13 13:19:57 [INFO] Running: /usr/bin/yum clean all
* 2024-07-13 13:19:57 [INFO]
* 2024-07-13 13:19:57 [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-13 13:19:57 [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2024-07-13 13:19:57 [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-13 13:19:57 [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-13 13:19:57 [INFO] : centos7els-rollout-6 extras updates
* 2024-07-13 13:19:57 [INFO] Cleaning up list of fastest mirrors
* 2024-07-13 13:19:57 [INFO] Other repos take up 548 k of disk space (use --verbose for details)
* 2024-07-13 13:19:57 [INFO]
* 2024-07-13 13:20:01 [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.
If you need assistance, open a ticket with cPanel Support, as outlined here:
https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-13 13:20:01 [ERROR] http://asi-fs-l.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
One of the configured repositories failed (CentOS-7-Base),
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=base ...
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 base
or
subscription-manager repos --disable=base
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=base.skip_if_unavailable=true
failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-l.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-13 13:20:01 [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-13 13:20:01 [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6bn3aKD1Jp/ea_profile.json
* 2024-07-13 13:20:04 [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6bn3aKD1Jp/ea_profile.json at /scripts/elevate-cpanel line 5992.
* 2024-07-13 13:20:04 [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
[root@vmi724241 ~]#
-
Hi,
The yum errors are likely occurring due to CentOS 7 reaching end of life, as their developers have since removed their mirrors from the internet. We have an article below detailing how you can work around this:
0 -
I have finished the Elevation process with errors. I have checked that link and my repos are identical, however a yum-update shows erros:
# yum update
CentOS 7 ELS - Gradual Rollout Slot 4 176 B/s | 153 B 00:00
CentOS 7 ELS - Gradual Rollout Slot 5 176 B/s | 153 B 00:00
CentOS 7 ELS - Gradual Rollout Slot 6 176 B/s | 153 B 00:00
Last metadata expiration check: 1:18:23 ago on Mon 15 Jul 2024 01:12:33 AM CEST.
Error:
Problem 1: cannot install the best update candidate for package bind-32:9.11.36-14.el8_10.x86_64
- nothing provides python-ply needed by bind-33:9.11.4-26.P2.el7_9.15.tuxcare.els1.x86_64 from centos7-els
- nothing provides policycoreutils-python needed by bind-33:9.11.4-26.P2.el7_9.15.tuxcare.els1.x86_64 from centos7-els
Problem 2: package dhcp-client-12:4.3.6-50.el8_10.x86_64 from @System requires libdns-export.so.1115()(64bit), but none of the providers can be installed
- package dhcp-client-12:4.3.6-50.el8_10.x86_64 from @System requires libirs-export.so.161()(64bit), but none of the providers can be installed
... (long)and a yum check-update shows:
CentOS 7 ELS - Gradual Rollout Slot 1 176 B/s | 153 B 00:00
CentOS 7 ELS - Gradual Rollout Slot 2 175 B/s | 153 B 00:00
CentOS 7 ELS - Gradual Rollout Slot 3 175 B/s | 153 B 00:00
CentOS 7 ELS - Gradual Rollout Slot 4 177 B/s | 153 B 00:00
CentOS 7 ELS - Gradual Rollout Slot 5 177 B/s | 153 B 00:00
CentOS 7 ELS - Gradual Rollout Slot 6 177 B/s | 153 B 00:00
Last metadata expiration check: 0:00:17 ago on Mon 15 Jul 2024 02:35:31 AM CEST.
ai-bolit.x86_64 1:32.1.11-1.el8 imunify360-rollout-5
alt-curl.x86_64 7.64.0-2.el8 imunify360
alt-libcurl.x86_64 7.64.0-2.el8 imunify360
alt-libssh2.x86_64 1.8.0-5.el8 imunify360
alt-openssl-libs.x86_64 1:1.0.2k-2.el8.cloudlinux.10 imunify360
alt-php-config.noarch 1-39.el8 imunify360
alt-python311-pip-wheel.noarch 21.3.1-2.el8 imunify360
alt-python311-setuptools-wheel.noarch 65.6.3-1.el8 imunify360
alt-python38.x86_64 3.8.12-2.el8 imunify360
alt-python38-PyYAML.x86_64 5.4.1-1.el8 imunify360
alt-python38-aiodns.noarch 3.0.0-2.el8 imunify360
alt-python38-aiohttp.x86_64 3.7.4-1.el8 imunify360
alt-python38-async-lru.noarch 1.0.2-1.el8 imunify360
alt-python38-async-timeout.noarch 1.3.0-1.el8 imunify360
alt-python38-attrs.noarch 17.4.0-1.el8 imunify360
alt-python38-blinker.noarch 1.4-2.el8 imunify360
alt-python38-cached_property.noarch 1.3.0-4.el8 imunify360
alt-python38-cerberus.noarch 1.3.4-2.el8 imunify360
alt-python38-certifi.noarch 2018.04.16-1.el8 imunify360
alt-python38-cffi.x86_64 1.14.0-1.el8 imunify360
alt-python38-chardet.noarch 3.0.4-1.el8 imunify360
alt-python38-click.noarch 6.6-2.el8 imunify360
alt-python38-daemon.noarch 2.3.0-1.el8 imunify360
alt-python38-distro.noarch 1.6.0-1.el8 imunify360
alt-python38-funcsigs.noarch 1.0.2-3.el8 imunify360
alt-python38-humanize.noarch 3.12.0-1.el8.cloudlinux imunify360
alt-python38-idna.noarch 2.5-1.el8 imunify360
alt-python38-lockfile.noarch 0.12.2-2.el8 imunify360
alt-python38-mock.noarch 3.0.5-1.el8 imunify360
alt-python38-multidict.x86_64 5.1.0-5.el8 imunify360
alt-python38-pam.noarch 1.8.4-1.el8 imunify360
alt-python38-pbr.noarch 1.8.1-2.el8 imunify360
alt-python38-peewee.x86_64 2.8.4-1.el8 imunify360
alt-python38-peewee_migrate.noarch 0.6.4-2.el8 imunify360
alt-python38-pip-wheel.noarch 20.2.4-1.el8 imunify360
alt-python38-ply.noarch 3.8-1.el8 imunify360
alt-python38-psutil.x86_64 5.8.0-1.el8 imunify360
alt-python38-pycares.x86_64 4.1.2-1.el8 imunify360
alt-python38-pycparser.noarch 2.14-7.el8 imunify360
alt-python38-pyjwt.noarch 2.1.0-4.el8 imunify360
alt-python38-pysocks.noarch 1.5.7-2.el8 imunify360
alt-python38-sentry-sdk.noarch 0.7.10-1.el8 imunify360
alt-python38-setuptools.noarch 57.4.0-1.el8 imunify360
alt-python38-setuptools-wheel.noarch 57.4.0-1.el8 imunify360
alt-python38-six.noarch 1.12.0-1.el8 imunify360
alt-python38-typing-extensions.noarch 3.7.4.3-5.el8 imunify360
alt-python38-urllib3.noarch 1.26.6-3.el8 imunify360
alt-python38-yarl.x86_64 1.1.1-3.el8 imunify360
bind.x86_64 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
bind-devel.x86_64 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
bind-export-libs.x86_64 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
bind-libs.x86_64 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
bind-libs-lite.x86_64 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
bind-license.noarch 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
bind-lite-devel.x86_64 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
bind-utils.x86_64 33:9.11.4-26.P2.el7_9.15.tuxcare.els1 centos7-els
ca-certificates.noarch 2023.2.64_v7.0.306-72.el7_9.tuxcare.els1 centos7-els
cloudlinux-linksafe.noarch 1-1.24.el8What's the cause ?
0 -
We had this on a server after using Elevate - looks like the centos7-els-rollout repo is still enabled after the upgrade. Disabling that should sort the issue out.
0 -
How the centos7-els-rollout repos can be disabled exactly?. Is there some guide?
thanks
0 -
I wouldn't expect this to be different than any other repository:
0
Please sign in to leave a comment.
Comments
5 comments