MOON
Server: Apache
System: Linux cl1170g 4.19.62-mod-std-ipv6-64-rescue #828825 SMP Tue Jul 30 13:54:49 UTC 2019 x86_64
User: wh0f20bb (1057)
PHP: 5.6.40
Disabled: NONE
Upload Files
File: //var/log/elevate-cpanel.log
* 2026-05-01 21:30:55 (12041) [INFO] Self-update of script version 81 requested.
* 2026-05-01 21:30:55 (12063) [INFO] Script is up to date.
* 2026-05-01 21:30:56 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only
* 2026-05-01 21:30:56 (10960) [INFO] 
* 2026-05-01 21:34:25 (10990) [INFO] 
* 2026-05-01 21:34:25 (264) [ERROR] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.50) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.97.

* 2026-05-01 21:34:25 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2026-05-01 21:34:25 (10960) [INFO] 
* 2026-05-01 21:34:25 (264) [ERROR] *** Elevation Blocker detected: ***
The Imunify license is reporting that it is not currently valid.  Since
Imunify is installed on this system, a valid Imunify license is required
to ELevate to AlmaLinux 8.

* 2026-05-01 21:34:26 (4584) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2026-05-01 21:34:26 (4591) [INFO] You can manually upgrade your installation of MySQL using the following command:

    /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6

Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.

* 2026-05-01 21:34:26 (10959) [INFO] Running: /usr/bin/yum list extras
* 2026-05-01 21:34:26 (10960) [INFO] 
* 2026-05-01 21:34:38 (6899) [ERROR] 1 package(s) installed from unsupported YUM repo 'ovhkernel' from /etc/yum.repos.d/OVH-kernel.repo
* 2026-05-01 21:34:38 (264) [ERROR] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates
extras
centosplus
fasttrack

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2026-05-01 21:34:38 (10959) [INFO] Running: /usr/bin/yum makecache
* 2026-05-01 21:34:38 (10960) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2026-05-01 21:34:38 (10973) [INFO] Loading mirror speeds from cached hostfile
* 2026-05-01 21:34:38 (10973) [INFO] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2026-05-01 21:34:38 (10973) [INFO] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]  One of the configured repositories failed (Unknown),
* 2026-05-01 21:34:38 (10973) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2026-05-01 21:34:38 (10973) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2026-05-01 21:34:38 (10973) [INFO]         upstream. This is most often useful if you are using a newer
* 2026-05-01 21:34:38 (10973) [INFO]         distribution release than is supported by the repository (and the
* 2026-05-01 21:34:38 (10973) [INFO]         packages for the previous distribution release still work).
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]      3. Run the command with the repository temporarily disabled
* 2026-05-01 21:34:38 (10973) [INFO]             yum --disablerepo=<repoid> ...
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2026-05-01 21:34:38 (10973) [INFO]         will then just ignore the repository until you permanently enable it
* 2026-05-01 21:34:38 (10973) [INFO]         again or use --enablerepo for temporary usage:
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]             yum-config-manager --disable <repoid>
* 2026-05-01 21:34:38 (10973) [INFO]         or
* 2026-05-01 21:34:38 (10973) [INFO]             subscription-manager repos --disable=<repoid>
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2026-05-01 21:34:38 (10973) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2026-05-01 21:34:38 (10973) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2026-05-01 21:34:38 (10973) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2026-05-01 21:34:38 (10973) [INFO]         compromise:
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2026-05-01 21:34:38 (10973) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO] Cannot find a valid baseurl for repo: base/7/x86_64
* 2026-05-01 21:34:38 (10990) [INFO] 
* 2026-05-01 21:34:38 (6781) [WARN] Initial run of "yum makecache" failed: 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"


 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: base/7/x86_64
* 2026-05-01 21:34:38 (6782) [WARN] Running "yum clean all" in an attempt to fix yum
* 2026-05-01 21:34:38 (10959) [INFO] Running: /usr/bin/yum clean all
* 2026-05-01 21:34:38 (10960) [INFO] 
* 2026-05-01 21:34:38 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2026-05-01 21:34:38 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins alt-common base
* 2026-05-01 21:34:38 (10973) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2026-05-01 21:34:38 (10973) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2026-05-01 21:34:38 (10973) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2026-05-01 21:34:38 (10973) [INFO]               : mysql-connectors-community mysql-tools-community
* 2026-05-01 21:34:38 (10973) [INFO]               : mysql57-community ovhkernel updates wp-toolkit-cpanel
* 2026-05-01 21:34:38 (10973) [INFO]               : wp-toolkit-thirdparties
* 2026-05-01 21:34:38 (10973) [INFO] Cleaning up list of fastest mirrors
* 2026-05-01 21:34:38 (10973) [INFO] Other repos take up 225 M of disk space (use --verbose for details)
* 2026-05-01 21:34:38 (10990) [INFO] 
* 2026-05-01 21:34:38 (10959) [INFO] Running: /usr/bin/yum makecache
* 2026-05-01 21:34:38 (10960) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2026-05-01 21:34:39 (10973) [INFO] Determining fastest mirrors
* 2026-05-01 21:34:39 (10973) [INFO] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2026-05-01 21:34:39 (10973) [INFO] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]  One of the configured repositories failed (Unknown),
* 2026-05-01 21:34:39 (10973) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2026-05-01 21:34:39 (10973) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2026-05-01 21:34:39 (10973) [INFO]         upstream. This is most often useful if you are using a newer
* 2026-05-01 21:34:39 (10973) [INFO]         distribution release than is supported by the repository (and the
* 2026-05-01 21:34:39 (10973) [INFO]         packages for the previous distribution release still work).
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]      3. Run the command with the repository temporarily disabled
* 2026-05-01 21:34:39 (10973) [INFO]             yum --disablerepo=<repoid> ...
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2026-05-01 21:34:39 (10973) [INFO]         will then just ignore the repository until you permanently enable it
* 2026-05-01 21:34:39 (10973) [INFO]         again or use --enablerepo for temporary usage:
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]             yum-config-manager --disable <repoid>
* 2026-05-01 21:34:39 (10973) [INFO]         or
* 2026-05-01 21:34:39 (10973) [INFO]             subscription-manager repos --disable=<repoid>
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2026-05-01 21:34:39 (10973) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2026-05-01 21:34:39 (10973) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2026-05-01 21:34:39 (10973) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2026-05-01 21:34:39 (10973) [INFO]         compromise:
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2026-05-01 21:34:39 (10973) [INFO] 
* 2026-05-01 21:34:39 (10973) [INFO] Cannot find a valid baseurl for repo: base/7/x86_64
* 2026-05-01 21:34:39 (10990) [INFO] 
* 2026-05-01 21:34:39 (6791) [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/
* 2026-05-01 21:34:39 (6792) [ERROR] 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"


 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: base/7/x86_64
* 2026-05-01 21:34:39 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2026-05-01 21:34:39 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XEzaLXnp5e/ea_profile.json
* 2026-05-01 21:34:41 (551) [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/XEzaLXnp5e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071.
* 2026-05-01 21:34:41 (492) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/