%PDF- %PDF-
Mini Shell

Mini Shell

Direktori : /proc/self/root/var/log/
Upload File :
Create Path :
Current File : //proc/self/root/var/log/elevate-cpanel.log

* 2023-05-19 01:33:31 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-19 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-19 01:33:32 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-19 01:33:32 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-19 01:33:32 (4086) [INFO] 
* 2023-05-19 01:33:32 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-19 01:33:32 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-19 01:33:32 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-19 01:33:32 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-19 01:33:32 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-19 01:33:32 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-19 01:33:32 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-19 01:33:32 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-19 01:33:32 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-19 01:33:32 (4116) [INFO] 
* 2023-05-19 01:33:32 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-19 01:33:32 (4086) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-19 01:33:44 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-19 01:33:44 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-19 01:33:44 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-19 01:33:44 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-19 01:33:44 (4099) [INFO] Trying other mirror.
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-19 01:33:44 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-19 01:33:44 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-19 01:33:44 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-19 01:33:44 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-19 01:33:44 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-19 01:33:44 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-19 01:33:44 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-19 01:33:44 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-19 01:33:44 (4099) [INFO]         or
* 2023-05-19 01:33:44 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-19 01:33:44 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-19 01:33:44 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-19 01:33:44 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-19 01:33:44 (4099) [INFO]         compromise:
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-19 01:33:44 (4099) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-19 01:33:44 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-19 01:33:44 (4116) [INFO] 
* 2023-05-19 01:33:44 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-19 01:33:44 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-19 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-19 01:33:45 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-19 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-19 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-19 01:33:45 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-19 01:33:45 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-19 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-19 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-19 01:33:45 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-19 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-19 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-19 01:33:49 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-19 01:33:49 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-19 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-19 01:33:49 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-19 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-19 01:33:49 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-19 01:33:49 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hpdShD9Mss/ea_profile.json
* 2023-05-19 01:34:24 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hpdShD9Mss/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-19 01:34:24 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-20 01:34:28 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-20 01:34:29 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-20 01:34:29 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-20 01:34:29 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-20 01:34:29 (4086) [INFO] 
* 2023-05-20 01:34:29 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-20 01:34:30 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-20 01:34:30 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-20 01:34:30 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-20 01:34:30 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-20 01:34:30 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-20 01:34:30 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-20 01:34:30 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-20 01:34:30 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-20 01:34:30 (4116) [INFO] 
* 2023-05-20 01:34:30 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-20 01:34:30 (4086) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-20 01:34:50 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-20 01:34:50 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-20 01:34:50 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-20 01:34:50 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-20 01:34:50 (4099) [INFO] Trying other mirror.
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-20 01:34:50 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-20 01:34:50 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-20 01:34:50 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-20 01:34:50 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-20 01:34:50 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-20 01:34:50 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-20 01:34:50 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-20 01:34:50 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-20 01:34:50 (4099) [INFO]         or
* 2023-05-20 01:34:50 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-20 01:34:50 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-20 01:34:50 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-20 01:34:50 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-20 01:34:50 (4099) [INFO]         compromise:
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-20 01:34:50 (4099) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-20 01:34:50 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-20 01:34:50 (4116) [INFO] 
* 2023-05-20 01:34:50 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-20 01:34:50 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-20 01:34:50 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-20 01:34:52 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-20 01:34:52 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-20 01:34:52 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-20 01:34:52 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-20 01:34:52 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-20 01:34:52 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-20 01:34:52 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-20 01:34:52 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-20 01:34:52 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-20 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-20 01:34:59 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-20 01:34:59 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-20 01:34:59 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-20 01:34:59 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-20 01:34:59 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-20 01:34:59 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-20 01:34:59 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oHlXvrSZrF/ea_profile.json
* 2023-05-20 01:35:37 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oHlXvrSZrF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-20 01:35:37 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-21 01:34:08 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-21 01:34:09 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-21 01:34:09 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-21 01:34:09 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-21 01:34:09 (4086) [INFO] 
* 2023-05-21 01:34:09 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-21 01:34:09 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-21 01:34:09 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-21 01:34:09 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-21 01:34:09 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-21 01:34:09 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-21 01:34:09 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-21 01:34:09 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-21 01:34:09 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-21 01:34:09 (4116) [INFO] 
* 2023-05-21 01:34:09 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-21 01:34:09 (4086) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-21 01:34:23 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-21 01:34:23 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-21 01:34:23 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-21 01:34:23 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-21 01:34:23 (4099) [INFO] Trying other mirror.
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-21 01:34:23 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-21 01:34:23 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-21 01:34:23 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-21 01:34:23 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-21 01:34:23 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-21 01:34:23 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-21 01:34:23 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-21 01:34:23 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-21 01:34:23 (4099) [INFO]         or
* 2023-05-21 01:34:23 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-21 01:34:23 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-21 01:34:23 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-21 01:34:23 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-21 01:34:23 (4099) [INFO]         compromise:
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-21 01:34:23 (4099) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-21 01:34:23 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-21 01:34:23 (4116) [INFO] 
* 2023-05-21 01:34:23 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-21 01:34:23 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-21 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-21 01:34:24 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-21 01:34:24 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-21 01:34:24 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-21 01:34:24 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-21 01:34:24 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-21 01:34:24 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-21 01:34:24 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-21 01:34:24 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-21 01:34:24 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-21 01:34:24 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-21 01:34:30 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-21 01:34:30 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-21 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-21 01:34:30 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-21 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-21 01:34:30 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-21 01:34:30 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZntXrWIe9_/ea_profile.json
* 2023-05-21 01:35:04 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZntXrWIe9_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-21 01:35:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-22 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-22 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-22 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-22 01:33:39 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-22 01:33:39 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-22 01:33:39 (4086) [INFO] 
* 2023-05-22 01:33:39 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-22 01:33:39 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-22 01:33:39 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-22 01:33:39 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-22 01:33:39 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-22 01:33:39 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-22 01:33:39 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-22 01:33:40 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-22 01:33:40 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-22 01:33:40 (4116) [INFO] 
* 2023-05-22 01:33:40 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-22 01:33:40 (4086) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-22 01:33:56 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-22 01:33:56 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-22 01:33:56 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-22 01:33:56 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-22 01:33:56 (4099) [INFO] Trying other mirror.
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-22 01:33:56 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-22 01:33:56 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-22 01:33:56 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-22 01:33:56 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-22 01:33:56 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-22 01:33:56 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-22 01:33:56 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-22 01:33:56 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-22 01:33:56 (4099) [INFO]         or
* 2023-05-22 01:33:56 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-22 01:33:56 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-22 01:33:56 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-22 01:33:56 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-22 01:33:56 (4099) [INFO]         compromise:
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-22 01:33:56 (4099) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-22 01:33:56 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-22 01:33:56 (4116) [INFO] 
* 2023-05-22 01:33:56 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-22 01:33:56 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-22 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-22 01:33:57 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-22 01:33:57 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-22 01:33:57 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-22 01:33:57 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-22 01:33:57 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-22 01:33:57 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-22 01:33:57 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-22 01:33:57 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-22 01:33:57 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-22 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-22 01:34:03 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-22 01:34:03 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-22 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-22 01:34:03 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-22 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-22 01:34:03 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-22 01:34:03 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p_q2058bDl/ea_profile.json
* 2023-05-22 01:34:39 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p_q2058bDl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-22 01:34:39 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-23 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-23 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-23 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-23 01:34:52 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-23 01:34:52 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-23 01:34:52 (4086) [INFO] 
* 2023-05-23 01:34:53 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-23 01:34:53 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-23 01:34:53 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-23 01:34:53 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-23 01:34:53 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-23 01:34:53 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-23 01:34:53 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-23 01:34:53 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-23 01:34:53 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-23 01:34:53 (4116) [INFO] 
* 2023-05-23 01:34:53 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-23 01:34:53 (4086) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-23 01:35:09 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-23 01:35:09 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-23 01:35:09 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-23 01:35:09 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-23 01:35:09 (4099) [INFO] Trying other mirror.
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-23 01:35:09 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-23 01:35:09 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-23 01:35:09 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-23 01:35:09 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-23 01:35:09 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-23 01:35:09 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-23 01:35:09 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-23 01:35:09 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-23 01:35:09 (4099) [INFO]         or
* 2023-05-23 01:35:09 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-23 01:35:09 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-23 01:35:09 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-23 01:35:09 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-23 01:35:09 (4099) [INFO]         compromise:
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-23 01:35:09 (4099) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-23 01:35:09 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-23 01:35:09 (4116) [INFO] 
* 2023-05-23 01:35:09 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-23 01:35:09 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-23 01:35:09 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-23 01:35:10 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-23 01:35:10 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-23 01:35:10 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-23 01:35:10 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-23 01:35:10 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-23 01:35:10 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-23 01:35:10 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-23 01:35:10 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-23 01:35:10 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-23 01:35:10 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-23 01:35:16 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-23 01:35:16 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-23 01:35:16 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-23 01:35:16 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-23 01:35:16 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-23 01:35:17 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-23 01:35:17 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yuQ2GXo2YY/ea_profile.json
* 2023-05-23 01:35:53 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yuQ2GXo2YY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-23 01:35:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-24 01:33:30 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-24 01:33:30 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-24 01:33:30 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-24 01:33:30 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-24 01:33:30 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-24 01:33:30 (4086) [INFO] 
* 2023-05-24 01:33:31 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-24 01:33:31 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-24 01:33:31 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-24 01:33:31 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-24 01:33:31 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-24 01:33:31 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-24 01:33:31 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-24 01:33:31 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-24 01:33:31 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-24 01:33:31 (4116) [INFO] 
* 2023-05-24 01:33:31 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-24 01:33:31 (4086) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-24 01:33:44 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-24 01:33:44 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-24 01:33:44 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-24 01:33:44 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-24 01:33:44 (4099) [INFO] Trying other mirror.
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-24 01:33:44 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-24 01:33:44 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-24 01:33:44 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-24 01:33:44 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-24 01:33:44 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-24 01:33:44 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-24 01:33:44 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-24 01:33:44 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-24 01:33:44 (4099) [INFO]         or
* 2023-05-24 01:33:44 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-24 01:33:44 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-24 01:33:44 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-24 01:33:44 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-24 01:33:44 (4099) [INFO]         compromise:
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-24 01:33:44 (4099) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-24 01:33:44 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-24 01:33:44 (4116) [INFO] 
* 2023-05-24 01:33:44 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-24 01:33:44 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-24 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-24 01:33:45 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-24 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-24 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-24 01:33:45 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-24 01:33:45 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-24 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-24 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-24 01:33:45 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-24 01:33:45 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-24 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-24 01:33:49 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-24 01:33:49 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-24 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-24 01:33:49 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-24 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-24 01:33:49 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-24 01:33:49 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xEfPTQ_HB9/ea_profile.json
* 2023-05-24 01:34:23 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xEfPTQ_HB9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-24 01:34:23 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-25 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-25 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-25 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-25 01:33:41 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-25 01:33:41 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-25 01:33:41 (4086) [INFO] 
* 2023-05-25 01:33:41 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-25 01:33:41 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-25 01:33:41 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-25 01:33:41 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-25 01:33:41 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-25 01:33:41 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-25 01:33:41 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-25 01:33:41 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-25 01:33:41 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-25 01:33:41 (4116) [INFO] 
* 2023-05-25 01:33:41 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-25 01:33:41 (4086) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-25 01:33:55 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-25 01:33:55 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-25 01:33:55 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-25 01:33:55 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-25 01:33:55 (4099) [INFO] Trying other mirror.
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-25 01:33:55 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-25 01:33:55 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-25 01:33:55 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-25 01:33:55 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-25 01:33:55 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-25 01:33:55 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-25 01:33:55 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-25 01:33:55 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-25 01:33:55 (4099) [INFO]         or
* 2023-05-25 01:33:55 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-25 01:33:55 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-25 01:33:55 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-25 01:33:55 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-25 01:33:55 (4099) [INFO]         compromise:
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-25 01:33:55 (4099) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-25 01:33:55 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-25 01:33:55 (4116) [INFO] 
* 2023-05-25 01:33:55 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-25 01:33:55 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-25 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-25 01:33:56 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-25 01:33:56 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-25 01:33:56 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-25 01:33:56 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-25 01:33:56 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-25 01:33:56 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-25 01:33:56 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-25 01:33:56 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-25 01:33:56 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-25 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-25 01:34:00 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-25 01:34:00 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-25 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-25 01:34:00 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-25 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-25 01:34:00 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-25 01:34:00 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ML7LvcNQFG/ea_profile.json
* 2023-05-25 01:34:35 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ML7LvcNQFG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-25 01:34:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-26 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-26 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-26 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-26 01:33:36 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-26 01:33:36 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-26 01:33:36 (4086) [INFO] 
* 2023-05-26 01:33:36 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-26 01:33:36 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-26 01:33:36 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-26 01:33:36 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-26 01:33:36 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-26 01:33:36 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-26 01:33:36 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-26 01:33:36 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-26 01:33:36 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-26 01:33:36 (4116) [INFO] 
* 2023-05-26 01:33:36 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-26 01:33:36 (4086) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-26 01:33:52 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-26 01:33:52 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-26 01:33:52 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-26 01:33:52 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-26 01:33:52 (4099) [INFO] Trying other mirror.
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-26 01:33:52 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-26 01:33:52 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-26 01:33:52 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-26 01:33:52 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-26 01:33:52 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-26 01:33:52 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-26 01:33:52 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-26 01:33:52 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-26 01:33:52 (4099) [INFO]         or
* 2023-05-26 01:33:52 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-26 01:33:52 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-26 01:33:52 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-26 01:33:52 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-26 01:33:52 (4099) [INFO]         compromise:
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-26 01:33:52 (4099) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-26 01:33:52 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-26 01:33:52 (4116) [INFO] 
* 2023-05-26 01:33:52 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-26 01:33:52 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-26 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-26 01:33:53 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-26 01:33:53 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-26 01:33:53 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-26 01:33:53 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-26 01:33:53 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-26 01:33:53 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-26 01:33:53 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-26 01:33:53 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-26 01:33:53 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-26 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-26 01:33:57 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-26 01:33:57 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-26 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-26 01:33:57 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-26 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-26 01:33:57 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-26 01:33:57 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bMP_5RSdnX/ea_profile.json
* 2023-05-26 01:34:31 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bMP_5RSdnX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-26 01:34:31 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-27 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-27 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-27 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-27 01:34:01 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-27 01:34:01 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-27 01:34:01 (4086) [INFO] 
* 2023-05-27 01:34:02 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-27 01:34:02 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-27 01:34:02 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-27 01:34:02 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-27 01:34:02 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-27 01:34:02 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-27 01:34:02 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-27 01:34:02 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-27 01:34:02 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-27 01:34:02 (4116) [INFO] 
* 2023-05-27 01:34:02 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-27 01:34:02 (4086) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-27 01:34:08 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-27 01:34:08 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-27 01:34:08 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-27 01:34:08 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-27 01:34:08 (4099) [INFO] Trying other mirror.
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-27 01:34:08 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-27 01:34:08 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-27 01:34:08 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-27 01:34:08 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-27 01:34:08 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-27 01:34:08 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-27 01:34:08 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-27 01:34:08 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-27 01:34:08 (4099) [INFO]         or
* 2023-05-27 01:34:08 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-27 01:34:08 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-27 01:34:08 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-27 01:34:08 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-27 01:34:08 (4099) [INFO]         compromise:
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-27 01:34:08 (4099) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-27 01:34:08 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-27 01:34:08 (4116) [INFO] 
* 2023-05-27 01:34:08 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-27 01:34:08 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-27 01:34:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-27 01:34:10 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-27 01:34:10 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-27 01:34:10 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-27 01:34:10 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-27 01:34:10 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-27 01:34:10 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-27 01:34:10 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-27 01:34:10 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-27 01:34:10 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-27 01:34:10 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-27 01:34:12 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-27 01:34:12 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-27 01:34:12 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-27 01:34:12 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-27 01:34:12 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-27 01:34:12 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-27 01:34:12 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IKlUPFMiOw/ea_profile.json
* 2023-05-27 01:34:46 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IKlUPFMiOw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-27 01:34:46 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-29 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-29 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-29 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-29 01:33:35 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-29 01:33:35 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-29 01:33:35 (4086) [INFO] 
* 2023-05-29 01:33:35 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-29 01:33:35 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-29 01:33:35 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-29 01:33:35 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-29 01:33:35 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-29 01:33:35 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-29 01:33:35 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-29 01:33:35 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-29 01:33:35 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-29 01:33:35 (4116) [INFO] 
* 2023-05-29 01:33:35 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-29 01:33:35 (4086) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-29 01:33:47 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-29 01:33:47 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-29 01:33:47 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-29 01:33:47 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-29 01:33:47 (4099) [INFO] Trying other mirror.
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-29 01:33:47 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-29 01:33:47 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-29 01:33:47 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-29 01:33:47 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-29 01:33:47 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-29 01:33:47 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-29 01:33:47 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-29 01:33:47 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-29 01:33:47 (4099) [INFO]         or
* 2023-05-29 01:33:47 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-29 01:33:47 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-29 01:33:47 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-29 01:33:47 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-29 01:33:47 (4099) [INFO]         compromise:
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-29 01:33:47 (4099) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-29 01:33:47 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-29 01:33:47 (4116) [INFO] 
* 2023-05-29 01:33:47 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-29 01:33:47 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-29 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-29 01:33:48 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-29 01:33:48 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-29 01:33:48 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-29 01:33:48 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-29 01:33:48 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-29 01:33:48 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-29 01:33:48 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-29 01:33:48 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-29 01:33:48 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-29 01:33:48 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-29 01:33:51 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-29 01:33:51 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-29 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-29 01:33:51 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-29 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-29 01:33:52 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-29 01:33:52 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p0yDHFd519/ea_profile.json
* 2023-05-29 01:34:26 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p0yDHFd519/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-29 01:34:26 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-30 01:33:31 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-30 01:33:31 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-30 01:33:31 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-30 01:33:31 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-30 01:33:31 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-30 01:33:31 (4086) [INFO] 
* 2023-05-30 01:33:31 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-30 01:33:31 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-30 01:33:31 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-30 01:33:31 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-30 01:33:31 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-30 01:33:31 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-30 01:33:31 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-30 01:33:31 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-30 01:33:31 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-30 01:33:31 (4116) [INFO] 
* 2023-05-30 01:33:31 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-30 01:33:31 (4086) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-30 01:33:46 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-30 01:33:46 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-30 01:33:46 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-30 01:33:46 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-30 01:33:46 (4099) [INFO] Trying other mirror.
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-30 01:33:46 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-30 01:33:46 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-30 01:33:46 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-30 01:33:46 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-30 01:33:46 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-30 01:33:46 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-30 01:33:46 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-30 01:33:46 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-30 01:33:46 (4099) [INFO]         or
* 2023-05-30 01:33:46 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-30 01:33:46 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-30 01:33:46 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-30 01:33:46 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-30 01:33:46 (4099) [INFO]         compromise:
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-30 01:33:46 (4099) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-30 01:33:46 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-30 01:33:46 (4116) [INFO] 
* 2023-05-30 01:33:46 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-30 01:33:46 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-30 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-30 01:33:47 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-30 01:33:47 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-30 01:33:47 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-30 01:33:47 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-30 01:33:47 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-30 01:33:47 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-30 01:33:47 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-30 01:33:47 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-30 01:33:47 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-30 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-30 01:33:56 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-30 01:33:56 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-30 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-30 01:33:56 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-30 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-30 01:33:56 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-30 01:33:56 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1W8xbYFs3x/ea_profile.json
* 2023-05-30 01:34:30 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1W8xbYFs3x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-30 01:34:30 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-31 01:35:24 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-05-31 01:35:24 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-31 01:35:24 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-05-31 01:35:24 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-31 01:35:24 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-31 01:35:24 (4086) [INFO] 
* 2023-05-31 01:35:24 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-31 01:35:25 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-05-31 01:35:25 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-05-31 01:35:25 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-05-31 01:35:25 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-05-31 01:35:25 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-05-31 01:35:25 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-05-31 01:35:25 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-05-31 01:35:25 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-05-31 01:35:25 (4116) [INFO] 
* 2023-05-31 01:35:25 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-31 01:35:25 (4086) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-05-31 01:35:32 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-05-31 01:35:32 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-05-31 01:35:32 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-05-31 01:35:32 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-31 01:35:32 (4099) [INFO] Trying other mirror.
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-05-31 01:35:32 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-31 01:35:32 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-31 01:35:32 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-31 01:35:32 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-31 01:35:32 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-31 01:35:32 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-31 01:35:32 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-31 01:35:32 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-05-31 01:35:32 (4099) [INFO]         or
* 2023-05-31 01:35:32 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-31 01:35:32 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-31 01:35:32 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-31 01:35:32 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-31 01:35:32 (4099) [INFO]         compromise:
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-05-31 01:35:32 (4099) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-05-31 01:35:32 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-31 01:35:32 (4116) [INFO] 
* 2023-05-31 01:35:32 (4099) [INFO] Is this ok [y/N]: 
* 2023-05-31 01:35:32 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-31 01:35:32 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-31 01:35:33 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-05-31 01:35:33 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-05-31 01:35:33 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-05-31 01:35:33 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-05-31 01:35:33 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-05-31 01:35:33 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-05-31 01:35:33 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-05-31 01:35:33 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-05-31 01:35:33 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-05-31 01:35:33 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-05-31 01:35:36 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-31 01:35:36 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-05-31 01:35:36 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-31 01:35:36 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-05-31 01:35:36 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-05-31 01:35:36 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-31 01:35:36 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EGApg_z6L9/ea_profile.json
* 2023-05-31 01:36:10 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EGApg_z6L9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-05-31 01:36:10 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-06-01 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-01 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-06-01 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-01 01:33:36 (1699) [INFO] Checking if your system is up to date: 
* 2023-06-01 01:33:36 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-06-01 01:33:36 (4086) [INFO] 
* 2023-06-01 01:33:37 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-01 01:33:37 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-01 01:33:37 (4099) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-01 01:33:37 (4099) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-01 01:33:37 (4099) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-01 01:33:37 (4099) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-01 01:33:37 (4099) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-01 01:33:37 (4099) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-01 01:33:37 (4099) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-01 01:33:37 (4116) [INFO] 
* 2023-06-01 01:33:37 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-01 01:33:37 (4086) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-01 01:33:51 (4099) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-01 01:33:51 (4099) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-01 01:33:51 (4099) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-01 01:33:51 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-01 01:33:51 (4099) [INFO] Trying other mirror.
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-01 01:33:51 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-01 01:33:51 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-01 01:33:51 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-01 01:33:51 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-01 01:33:51 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-01 01:33:51 (4099) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-01 01:33:51 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-01 01:33:51 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-01 01:33:51 (4099) [INFO]         or
* 2023-06-01 01:33:51 (4099) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-01 01:33:51 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-01 01:33:51 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-01 01:33:51 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-01 01:33:51 (4099) [INFO]         compromise:
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-01 01:33:51 (4099) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-01 01:33:51 (4099) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-01 01:33:51 (4116) [INFO] 
* 2023-06-01 01:33:51 (4099) [INFO] Is this ok [y/N]: 
* 2023-06-01 01:33:51 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-01 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-01 01:33:52 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-01 01:33:52 (1635) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-01 01:33:52 (1635) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-01 01:33:52 (1624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-01 01:33:52 (1624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-01 01:33:52 (1635) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-01 01:33:52 (1635) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-01 01:33:52 (1624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-01 01:33:52 (1635) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-01 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-01 01:33:55 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-01 01:33:55 (1566) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-01 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-01 01:33:55 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-01 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-01 01:33:55 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-01 01:33:55 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oA9gRDy9M1/ea_profile.json
* 2023-06-01 01:34:29 (296) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oA9gRDy9M1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2237.
* 2023-06-01 01:34:29 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-06-02 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-02 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-06-02 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-02 01:33:32 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-02 01:33:32 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-02 01:33:32 (4089) [INFO] 
* 2023-06-02 01:33:32 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-02 01:33:32 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-02 01:33:32 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-02 01:33:32 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-02 01:33:32 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-02 01:33:32 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-02 01:33:32 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-02 01:33:32 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-02 01:33:33 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-02 01:33:33 (4119) [INFO] 
* 2023-06-02 01:33:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-02 01:33:33 (4089) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-02 01:33:50 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-02 01:33:50 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-02 01:33:50 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-02 01:33:50 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-02 01:33:50 (4102) [INFO] Trying other mirror.
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-02 01:33:50 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-02 01:33:50 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-02 01:33:50 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-02 01:33:50 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-02 01:33:50 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-02 01:33:50 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-02 01:33:50 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-02 01:33:50 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-02 01:33:50 (4102) [INFO]         or
* 2023-06-02 01:33:50 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-02 01:33:50 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-02 01:33:50 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-02 01:33:50 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-02 01:33:50 (4102) [INFO]         compromise:
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-02 01:33:50 (4102) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-02 01:33:50 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-02 01:33:50 (4119) [INFO] 
* 2023-06-02 01:33:50 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-02 01:33:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-02 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-02 01:33:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-02 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-02 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-02 01:33:51 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-02 01:33:51 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-02 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-02 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-02 01:33:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-02 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-02 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-02 01:33:55 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-02 01:33:55 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-02 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-02 01:33:55 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-02 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-02 01:33:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-02 01:33:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QhZuhN3prR/ea_profile.json
* 2023-06-02 01:34:30 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QhZuhN3prR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-02 01:34:30 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-03 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-03 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2023-06-03 01:34:04 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-03 01:34:04 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-03 01:34:04 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-03 01:34:04 (4089) [INFO] 
* 2023-06-03 01:34:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-03 01:34:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-03 01:34:04 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-03 01:34:04 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-03 01:34:04 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-03 01:34:04 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-03 01:34:04 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-03 01:34:04 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-03 01:34:04 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-03 01:34:04 (4119) [INFO] 
* 2023-06-03 01:34:04 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-03 01:34:04 (4089) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-03 01:34:14 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-03 01:34:14 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-03 01:34:14 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-03 01:34:14 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-03 01:34:14 (4102) [INFO] Trying other mirror.
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-03 01:34:14 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-03 01:34:14 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-03 01:34:14 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-03 01:34:14 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-03 01:34:14 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-03 01:34:14 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-03 01:34:14 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-03 01:34:14 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-03 01:34:14 (4102) [INFO]         or
* 2023-06-03 01:34:14 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-03 01:34:14 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-03 01:34:14 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-03 01:34:14 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-03 01:34:14 (4102) [INFO]         compromise:
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-03 01:34:14 (4102) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-03 01:34:14 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-03 01:34:14 (4119) [INFO] 
* 2023-06-03 01:34:14 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-03 01:34:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-03 01:34:14 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-03 01:34:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-03 01:34:15 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-03 01:34:15 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-03 01:34:15 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-03 01:34:15 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-03 01:34:15 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-03 01:34:15 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-03 01:34:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-03 01:34:15 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-03 01:34:15 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-03 01:34:18 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-03 01:34:18 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-03 01:34:18 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-03 01:34:18 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-03 01:34:18 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-03 01:34:19 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-03 01:34:19 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o6lzkodH2g/ea_profile.json
* 2023-06-03 01:34:53 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o6lzkodH2g/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-03 01:34:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-04 01:34:20 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-04 01:34:20 (153) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2023-06-04 01:34:20 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-04 01:34:20 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-04 01:34:20 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-04 01:34:20 (4089) [INFO] 
* 2023-06-04 01:34:20 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-04 01:34:20 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-04 01:34:20 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-04 01:34:20 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-04 01:34:20 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-04 01:34:20 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-04 01:34:20 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-04 01:34:20 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-04 01:34:21 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-04 01:34:21 (4119) [INFO] 
* 2023-06-04 01:34:21 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-04 01:34:21 (4089) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-04 01:34:36 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-04 01:34:36 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-04 01:34:36 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-04 01:34:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-04 01:34:36 (4102) [INFO] Trying other mirror.
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-04 01:34:36 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-04 01:34:36 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-04 01:34:36 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-04 01:34:36 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-04 01:34:36 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-04 01:34:36 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-04 01:34:36 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-04 01:34:36 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-04 01:34:36 (4102) [INFO]         or
* 2023-06-04 01:34:36 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-04 01:34:36 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-04 01:34:36 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-04 01:34:36 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-04 01:34:36 (4102) [INFO]         compromise:
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-04 01:34:36 (4102) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-04 01:34:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-04 01:34:36 (4119) [INFO] 
* 2023-06-04 01:34:36 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-04 01:34:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-04 01:34:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-04 01:34:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-04 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-04 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-04 01:34:37 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-04 01:34:37 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-04 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-04 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-04 01:34:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-04 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-04 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-04 01:34:42 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-04 01:34:42 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-04 01:34:42 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-04 01:34:42 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-04 01:34:42 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-04 01:34:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-04 01:34:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ssq0nSVqG5/ea_profile.json
* 2023-06-04 01:35:16 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ssq0nSVqG5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-04 01:35:16 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-05 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-05 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2023-06-05 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-05 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-05 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-05 01:33:33 (4089) [INFO] 
* 2023-06-05 01:33:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-05 01:33:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-05 01:33:34 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-05 01:33:34 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-05 01:33:34 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-05 01:33:34 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-05 01:33:34 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-05 01:33:34 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-05 01:33:34 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-05 01:33:34 (4119) [INFO] 
* 2023-06-05 01:33:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-05 01:33:34 (4089) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-05 01:33:44 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-05 01:33:44 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-05 01:33:44 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-05 01:33:44 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-05 01:33:44 (4102) [INFO] Trying other mirror.
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-05 01:33:44 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-05 01:33:44 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-05 01:33:44 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-05 01:33:44 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-05 01:33:44 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-05 01:33:44 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-05 01:33:44 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-05 01:33:44 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-05 01:33:44 (4102) [INFO]         or
* 2023-06-05 01:33:44 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-05 01:33:44 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-05 01:33:44 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-05 01:33:44 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-05 01:33:44 (4102) [INFO]         compromise:
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-05 01:33:44 (4102) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-05 01:33:44 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-05 01:33:44 (4119) [INFO] 
* 2023-06-05 01:33:44 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-05 01:33:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-05 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-05 01:33:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-05 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-05 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-05 01:33:45 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-05 01:33:45 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-05 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-05 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-05 01:33:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-05 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-05 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-05 01:33:47 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-05 01:33:47 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-05 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-05 01:33:47 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-05 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-05 01:33:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-05 01:33:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k3fwRfAMa1/ea_profile.json
* 2023-06-05 01:34:21 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k3fwRfAMa1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-05 01:34:21 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-06 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-06 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-06 01:33:52 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-06 01:33:52 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-06 01:33:52 (4089) [INFO] 
* 2023-06-06 01:33:53 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-06 01:33:53 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-06 01:33:53 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-06 01:33:53 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-06 01:33:53 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-06 01:33:53 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-06 01:33:53 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-06 01:33:53 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-06 01:33:53 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-06 01:33:53 (4119) [INFO] 
* 2023-06-06 01:33:53 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-06 01:33:53 (4089) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-06 01:34:10 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-06 01:34:10 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-06 01:34:10 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-06 01:34:10 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-06 01:34:10 (4102) [INFO] Trying other mirror.
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-06 01:34:10 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-06 01:34:10 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-06 01:34:10 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-06 01:34:10 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-06 01:34:10 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-06 01:34:10 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-06 01:34:10 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-06 01:34:10 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-06 01:34:10 (4102) [INFO]         or
* 2023-06-06 01:34:10 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-06 01:34:10 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-06 01:34:10 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-06 01:34:10 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-06 01:34:10 (4102) [INFO]         compromise:
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-06 01:34:10 (4102) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-06 01:34:10 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-06 01:34:10 (4119) [INFO] 
* 2023-06-06 01:34:10 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-06 01:34:10 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-06 01:34:10 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-06 01:34:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-06 01:34:11 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-06 01:34:11 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-06 01:34:11 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-06 01:34:11 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-06 01:34:11 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-06 01:34:11 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-06 01:34:11 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-06 01:34:11 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-06 01:34:11 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-06 01:34:25 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-06 01:34:25 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-06 01:34:25 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-06 01:34:25 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-06 01:34:25 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-06 01:34:25 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-06 01:34:25 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cvMX1h_e0j/ea_profile.json
* 2023-06-06 01:35:32 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cvMX1h_e0j/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-06 01:35:32 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-07 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-07 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-07 01:33:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-07 01:33:35 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-07 01:33:35 (4089) [INFO] 
* 2023-06-07 01:33:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-07 01:33:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-07 01:33:35 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-07 01:33:35 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-07 01:33:35 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-07 01:33:35 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-07 01:33:35 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-07 01:33:35 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-07 01:33:35 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-07 01:33:35 (4119) [INFO] 
* 2023-06-07 01:33:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-07 01:33:35 (4089) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-07 01:33:43 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-07 01:33:43 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-07 01:33:43 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-07 01:33:43 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-07 01:33:43 (4102) [INFO] Trying other mirror.
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-07 01:33:43 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-07 01:33:43 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-07 01:33:43 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-07 01:33:43 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-07 01:33:43 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-07 01:33:43 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-07 01:33:43 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-07 01:33:43 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-07 01:33:43 (4102) [INFO]         or
* 2023-06-07 01:33:43 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-07 01:33:43 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-07 01:33:43 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-07 01:33:43 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-07 01:33:43 (4102) [INFO]         compromise:
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-07 01:33:43 (4102) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-07 01:33:43 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-07 01:33:43 (4119) [INFO] 
* 2023-06-07 01:33:43 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-07 01:33:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-07 01:33:43 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-07 01:33:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-07 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-07 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-07 01:33:44 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-07 01:33:44 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-07 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-07 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-07 01:33:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-07 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-07 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-07 01:33:46 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-07 01:33:46 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-07 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-07 01:33:46 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-07 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-07 01:33:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-07 01:33:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L1PAULFM30/ea_profile.json
* 2023-06-07 01:33:51 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L1PAULFM30/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-07 01:33:51 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-08 01:33:27 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-08 01:33:27 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-08 01:33:27 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-08 01:33:27 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-08 01:33:27 (4089) [INFO] 
* 2023-06-08 01:33:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-08 01:33:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-08 01:33:28 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-08 01:33:28 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-08 01:33:28 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-08 01:33:28 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-08 01:33:28 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-08 01:33:28 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-08 01:33:28 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-08 01:33:28 (4119) [INFO] 
* 2023-06-08 01:33:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-08 01:33:28 (4089) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-08 01:33:40 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-08 01:33:40 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-08 01:33:40 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-08 01:33:40 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-08 01:33:40 (4102) [INFO] Trying other mirror.
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-08 01:33:40 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-08 01:33:40 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-08 01:33:40 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-08 01:33:40 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-08 01:33:40 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-08 01:33:40 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-08 01:33:40 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-08 01:33:40 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-08 01:33:40 (4102) [INFO]         or
* 2023-06-08 01:33:40 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-08 01:33:40 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-08 01:33:40 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-08 01:33:40 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-08 01:33:40 (4102) [INFO]         compromise:
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-08 01:33:40 (4102) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-08 01:33:40 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-08 01:33:40 (4119) [INFO] 
* 2023-06-08 01:33:40 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-08 01:33:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-08 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-08 01:33:42 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-08 01:33:42 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-08 01:33:42 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-08 01:33:42 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-08 01:33:42 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-08 01:33:42 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-08 01:33:42 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-08 01:33:42 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-08 01:33:42 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-08 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-08 01:33:45 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-08 01:33:45 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-08 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-08 01:33:45 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-08 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-08 01:33:45 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-08 01:33:45 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f_A6n_r_sK/ea_profile.json
* 2023-06-08 01:33:49 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f_A6n_r_sK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-08 01:33:49 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-09 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-09 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-09 01:33:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-09 01:33:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-09 01:33:39 (4089) [INFO] 
* 2023-06-09 01:33:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-09 01:33:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-09 01:33:39 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-09 01:33:39 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-09 01:33:39 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-09 01:33:39 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-09 01:33:39 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-09 01:33:39 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-09 01:33:39 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-09 01:33:39 (4119) [INFO] 
* 2023-06-09 01:33:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-09 01:33:39 (4089) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-09 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-09 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-09 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-09 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-09 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-09 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-09 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-09 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-09 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-09 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-09 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-09 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-09 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-09 01:33:53 (4102) [INFO]         or
* 2023-06-09 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-09 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-09 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-09 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-09 01:33:53 (4102) [INFO]         compromise:
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-09 01:33:53 (4102) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-09 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-09 01:33:53 (4119) [INFO] 
* 2023-06-09 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-09 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-09 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-09 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-09 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-09 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-09 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-09 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-09 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-09 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-09 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-09 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-09 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-09 01:33:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-09 01:33:58 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-09 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-09 01:33:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-09 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-09 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-09 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gXAOGypt8x/ea_profile.json
* 2023-06-09 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gXAOGypt8x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-09 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-10 01:34:06 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-10 01:34:06 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-10 01:34:06 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-10 01:34:06 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-10 01:34:06 (4089) [INFO] 
* 2023-06-10 01:34:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-10 01:34:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-10 01:34:07 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-10 01:34:07 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-10 01:34:07 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-10 01:34:07 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-10 01:34:07 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-10 01:34:07 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-10 01:34:07 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-10 01:34:07 (4119) [INFO] 
* 2023-06-10 01:34:07 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-10 01:34:07 (4089) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-10 01:34:23 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-10 01:34:23 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-10 01:34:23 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-10 01:34:23 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-10 01:34:23 (4102) [INFO] Trying other mirror.
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-10 01:34:23 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-10 01:34:23 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-10 01:34:23 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-10 01:34:23 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-10 01:34:23 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-10 01:34:23 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-10 01:34:23 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-10 01:34:23 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-10 01:34:23 (4102) [INFO]         or
* 2023-06-10 01:34:23 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-10 01:34:23 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-10 01:34:23 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-10 01:34:23 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-10 01:34:23 (4102) [INFO]         compromise:
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-10 01:34:23 (4102) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-10 01:34:23 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-10 01:34:23 (4119) [INFO] 
* 2023-06-10 01:34:23 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-10 01:34:23 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-10 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-10 01:34:24 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-10 01:34:24 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-10 01:34:24 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-10 01:34:24 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-10 01:34:24 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-10 01:34:24 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-10 01:34:24 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-10 01:34:24 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-10 01:34:24 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-10 01:34:24 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-10 01:34:27 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-10 01:34:27 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-10 01:34:27 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-10 01:34:27 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-10 01:34:27 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-10 01:34:27 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-10 01:34:27 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OMKSc1oY5n/ea_profile.json
* 2023-06-10 01:34:32 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OMKSc1oY5n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-10 01:34:32 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-11 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-11 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-11 01:34:02 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-11 01:34:02 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-11 01:34:02 (4089) [INFO] 
* 2023-06-11 01:34:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-11 01:34:03 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-11 01:34:03 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-11 01:34:03 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-11 01:34:03 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-11 01:34:03 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-11 01:34:03 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-11 01:34:03 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-11 01:34:03 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-11 01:34:03 (4119) [INFO] 
* 2023-06-11 01:34:03 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-11 01:34:03 (4089) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-11 01:34:16 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-11 01:34:16 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-11 01:34:16 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-11 01:34:16 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-11 01:34:16 (4102) [INFO] Trying other mirror.
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-11 01:34:16 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-11 01:34:16 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-11 01:34:16 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-11 01:34:16 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-11 01:34:16 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-11 01:34:16 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-11 01:34:16 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-11 01:34:16 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-11 01:34:16 (4102) [INFO]         or
* 2023-06-11 01:34:16 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-11 01:34:16 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-11 01:34:16 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-11 01:34:16 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-11 01:34:16 (4102) [INFO]         compromise:
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-11 01:34:16 (4102) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-11 01:34:16 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-11 01:34:16 (4119) [INFO] 
* 2023-06-11 01:34:16 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-11 01:34:16 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-11 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-11 01:34:17 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-11 01:34:17 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-11 01:34:17 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-11 01:34:17 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-11 01:34:17 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-11 01:34:17 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-11 01:34:17 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-11 01:34:17 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-11 01:34:17 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-11 01:34:17 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-11 01:34:19 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-11 01:34:19 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-11 01:34:19 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-11 01:34:19 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-11 01:34:19 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-11 01:34:19 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-11 01:34:19 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ArPYwET2ct/ea_profile.json
* 2023-06-11 01:34:25 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ArPYwET2ct/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-11 01:34:25 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-12 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-12 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-12 01:33:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-12 01:33:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-12 01:33:37 (4089) [INFO] 
* 2023-06-12 01:33:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-12 01:33:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-12 01:33:37 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-12 01:33:37 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-12 01:33:37 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-12 01:33:37 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-12 01:33:37 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-12 01:33:37 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-12 01:33:37 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-12 01:33:37 (4119) [INFO] 
* 2023-06-12 01:33:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-12 01:33:37 (4089) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-12 01:33:54 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-12 01:33:54 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-12 01:33:54 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-12 01:33:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-12 01:33:54 (4102) [INFO] Trying other mirror.
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-12 01:33:54 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-12 01:33:54 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-12 01:33:54 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-12 01:33:54 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-12 01:33:54 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-12 01:33:54 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-12 01:33:54 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-12 01:33:54 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-12 01:33:54 (4102) [INFO]         or
* 2023-06-12 01:33:54 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-12 01:33:54 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-12 01:33:54 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-12 01:33:54 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-12 01:33:54 (4102) [INFO]         compromise:
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-12 01:33:54 (4102) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-12 01:33:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-12 01:33:54 (4119) [INFO] 
* 2023-06-12 01:33:54 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-12 01:33:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-12 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-12 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-12 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-12 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-12 01:33:55 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-12 01:33:55 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-12 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-12 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-12 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-12 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-12 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-12 01:34:01 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-12 01:34:01 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-12 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-12 01:34:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-12 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-12 01:34:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-12 01:34:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fFGbdt4loM/ea_profile.json
* 2023-06-12 01:34:07 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fFGbdt4loM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-12 01:34:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-13 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-13 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-13 01:33:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-13 01:33:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-13 01:33:37 (4089) [INFO] 
* 2023-06-13 01:33:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-13 01:33:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-13 01:33:37 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-13 01:33:37 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-13 01:33:37 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-13 01:33:37 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-13 01:33:37 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-13 01:33:37 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-13 01:33:37 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-13 01:33:37 (4119) [INFO] 
* 2023-06-13 01:33:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-13 01:33:37 (4089) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-13 01:34:00 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-13 01:34:00 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-13 01:34:00 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-13 01:34:00 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-13 01:34:00 (4102) [INFO] Trying other mirror.
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-13 01:34:00 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-13 01:34:00 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-13 01:34:00 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-13 01:34:00 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-13 01:34:00 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-13 01:34:00 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-13 01:34:00 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-13 01:34:00 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-13 01:34:00 (4102) [INFO]         or
* 2023-06-13 01:34:00 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-13 01:34:00 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-13 01:34:00 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-13 01:34:00 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-13 01:34:00 (4102) [INFO]         compromise:
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-13 01:34:00 (4102) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-13 01:34:00 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-13 01:34:00 (4119) [INFO] 
* 2023-06-13 01:34:00 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-13 01:34:00 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-13 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-13 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-13 01:34:02 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-13 01:34:02 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-13 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-13 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-13 01:34:08 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-13 01:34:08 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-13 01:34:08 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-13 01:34:08 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-13 01:34:08 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-13 01:34:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-13 01:34:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HqAg2a2n_K/ea_profile.json
* 2023-06-13 01:34:13 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HqAg2a2n_K/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-13 01:34:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-14 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-14 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-14 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-14 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-14 01:33:33 (4089) [INFO] 
* 2023-06-14 01:33:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-14 01:33:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-14 01:33:33 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-14 01:33:33 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-14 01:33:33 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-14 01:33:33 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-14 01:33:33 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-14 01:33:33 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-14 01:33:33 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-14 01:33:33 (4119) [INFO] 
* 2023-06-14 01:33:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-14 01:33:33 (4089) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-14 01:33:57 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-14 01:33:57 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-14 01:33:57 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-14 01:33:57 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-14 01:33:57 (4102) [INFO] Trying other mirror.
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-14 01:33:57 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-14 01:33:57 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-14 01:33:57 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-14 01:33:57 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-14 01:33:57 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-14 01:33:57 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-14 01:33:57 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-14 01:33:57 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-14 01:33:57 (4102) [INFO]         or
* 2023-06-14 01:33:57 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-14 01:33:57 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-14 01:33:57 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-14 01:33:57 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-14 01:33:57 (4102) [INFO]         compromise:
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-14 01:33:57 (4102) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-14 01:33:57 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-14 01:33:57 (4119) [INFO] 
* 2023-06-14 01:33:57 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-14 01:33:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-14 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-14 01:33:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-14 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-14 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-14 01:33:58 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-14 01:33:58 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-14 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-14 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-14 01:33:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-14 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-14 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-14 01:34:05 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-14 01:34:05 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-14 01:34:05 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-14 01:34:05 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-14 01:34:05 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-14 01:34:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-14 01:34:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZukrBOAWZU/ea_profile.json
* 2023-06-14 01:34:10 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZukrBOAWZU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-14 01:34:10 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-15 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-15 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-15 01:33:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-15 01:33:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-15 01:33:40 (4089) [INFO] 
* 2023-06-15 01:33:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-15 01:33:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-15 01:33:41 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-15 01:33:41 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-15 01:33:41 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-15 01:33:41 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-15 01:33:41 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-15 01:33:41 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-15 01:33:41 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-15 01:33:41 (4119) [INFO] 
* 2023-06-15 01:33:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-15 01:33:41 (4089) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-15 01:33:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-15 01:33:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-15 01:33:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-15 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-15 01:33:52 (4102) [INFO] Trying other mirror.
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-15 01:33:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-15 01:33:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-15 01:33:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-15 01:33:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-15 01:33:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-15 01:33:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-15 01:33:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-15 01:33:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-15 01:33:52 (4102) [INFO]         or
* 2023-06-15 01:33:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-15 01:33:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-15 01:33:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-15 01:33:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-15 01:33:52 (4102) [INFO]         compromise:
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-15 01:33:52 (4102) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-15 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-15 01:33:52 (4119) [INFO] 
* 2023-06-15 01:33:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-15 01:33:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-15 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-15 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-15 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-15 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-15 01:33:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-15 01:33:53 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-15 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-15 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-15 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-15 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-15 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-15 01:33:56 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-15 01:33:56 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-15 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-15 01:33:56 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-15 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-15 01:33:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-15 01:33:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zJBszoGxDz/ea_profile.json
* 2023-06-15 01:34:01 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zJBszoGxDz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-15 01:34:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-16 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-16 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-16 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-16 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-16 01:33:33 (4089) [INFO] 
* 2023-06-16 01:33:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-16 01:33:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-16 01:33:33 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-16 01:33:33 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-16 01:33:33 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-16 01:33:33 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-16 01:33:33 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-16 01:33:33 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-16 01:33:33 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-16 01:33:33 (4119) [INFO] 
* 2023-06-16 01:33:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-16 01:33:33 (4089) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-16 01:33:47 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-16 01:33:47 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-16 01:33:47 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-16 01:33:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-16 01:33:47 (4102) [INFO] Trying other mirror.
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-16 01:33:47 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-16 01:33:47 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-16 01:33:47 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-16 01:33:47 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-16 01:33:47 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-16 01:33:47 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-16 01:33:47 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-16 01:33:47 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-16 01:33:47 (4102) [INFO]         or
* 2023-06-16 01:33:47 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-16 01:33:47 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-16 01:33:47 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-16 01:33:47 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-16 01:33:47 (4102) [INFO]         compromise:
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-16 01:33:47 (4102) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-16 01:33:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-16 01:33:47 (4119) [INFO] 
* 2023-06-16 01:33:47 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-16 01:33:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-16 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-16 01:33:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-16 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-16 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-16 01:33:49 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-16 01:33:49 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-16 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-16 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-16 01:33:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-16 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-16 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-16 01:33:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-16 01:33:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-16 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-16 01:33:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-16 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-16 01:33:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-16 01:33:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m4JZjelqWF/ea_profile.json
* 2023-06-16 01:34:02 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m4JZjelqWF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-16 01:34:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-17 01:34:06 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-17 01:34:07 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-17 01:34:07 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-17 01:34:07 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-17 01:34:07 (4089) [INFO] 
* 2023-06-17 01:34:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-17 01:34:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-17 01:34:07 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-17 01:34:07 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-17 01:34:07 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-17 01:34:07 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-17 01:34:07 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-17 01:34:07 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-17 01:34:07 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-17 01:34:07 (4119) [INFO] 
* 2023-06-17 01:34:07 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-17 01:34:07 (4089) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-17 01:34:21 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-17 01:34:21 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-17 01:34:21 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-17 01:34:21 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-17 01:34:21 (4102) [INFO] Trying other mirror.
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-17 01:34:21 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-17 01:34:21 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-17 01:34:21 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-17 01:34:21 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-17 01:34:21 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-17 01:34:21 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-17 01:34:21 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-17 01:34:21 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-17 01:34:21 (4102) [INFO]         or
* 2023-06-17 01:34:21 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-17 01:34:21 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-17 01:34:21 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-17 01:34:21 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-17 01:34:21 (4102) [INFO]         compromise:
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-17 01:34:21 (4102) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-17 01:34:21 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-17 01:34:21 (4119) [INFO] 
* 2023-06-17 01:34:21 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-17 01:34:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-17 01:34:21 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-17 01:34:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-17 01:34:23 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-17 01:34:23 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-17 01:34:23 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-17 01:34:23 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-17 01:34:23 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-17 01:34:23 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-17 01:34:23 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-17 01:34:23 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-17 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-17 01:34:31 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-17 01:34:31 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-17 01:34:31 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-17 01:34:31 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-17 01:34:31 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-17 01:34:32 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-17 01:34:32 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ios7hfYXkC/ea_profile.json
* 2023-06-17 01:34:38 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ios7hfYXkC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-17 01:34:38 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-18 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-18 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-18 01:34:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-18 01:34:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-18 01:34:30 (4089) [INFO] 
* 2023-06-18 01:34:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-18 01:34:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-18 01:34:31 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-18 01:34:31 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-18 01:34:31 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-18 01:34:31 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-18 01:34:31 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-18 01:34:31 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-18 01:34:31 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-18 01:34:31 (4119) [INFO] 
* 2023-06-18 01:34:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-18 01:34:31 (4089) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-18 01:34:54 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-18 01:34:54 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-18 01:34:54 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-18 01:34:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-18 01:34:54 (4102) [INFO] Trying other mirror.
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-18 01:34:54 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-18 01:34:54 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-18 01:34:54 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-18 01:34:54 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-18 01:34:54 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-18 01:34:54 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-18 01:34:54 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-18 01:34:54 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-18 01:34:54 (4102) [INFO]         or
* 2023-06-18 01:34:54 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-18 01:34:54 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-18 01:34:54 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-18 01:34:54 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-18 01:34:54 (4102) [INFO]         compromise:
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-18 01:34:54 (4102) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-18 01:34:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-18 01:34:54 (4119) [INFO] 
* 2023-06-18 01:34:54 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-18 01:34:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-18 01:34:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-18 01:34:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-18 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-18 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-18 01:34:55 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-18 01:34:55 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-18 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-18 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-18 01:34:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-18 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-18 01:34:55 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-18 01:35:16 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-18 01:35:16 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-18 01:35:16 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-18 01:35:16 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-18 01:35:16 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-18 01:35:16 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-18 01:35:16 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UD8tkewXNi/ea_profile.json
* 2023-06-18 01:35:35 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UD8tkewXNi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-18 01:35:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-19 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-19 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-19 01:33:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-19 01:33:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-19 01:33:38 (4089) [INFO] 
* 2023-06-19 01:33:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-19 01:33:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-19 01:33:38 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-19 01:33:38 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-19 01:33:38 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-19 01:33:38 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-19 01:33:38 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-19 01:33:38 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-19 01:33:38 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-19 01:33:38 (4119) [INFO] 
* 2023-06-19 01:33:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-19 01:33:38 (4089) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-19 01:33:47 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-19 01:33:47 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-19 01:33:47 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-19 01:33:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-19 01:33:47 (4102) [INFO] Trying other mirror.
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-19 01:33:47 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-19 01:33:47 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-19 01:33:47 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-19 01:33:47 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-19 01:33:47 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-19 01:33:47 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-19 01:33:47 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-19 01:33:47 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-19 01:33:47 (4102) [INFO]         or
* 2023-06-19 01:33:47 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-19 01:33:47 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-19 01:33:47 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-19 01:33:47 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-19 01:33:47 (4102) [INFO]         compromise:
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-19 01:33:47 (4102) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-19 01:33:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-19 01:33:47 (4119) [INFO] 
* 2023-06-19 01:33:47 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-19 01:33:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-19 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-19 01:33:48 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-19 01:33:48 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-19 01:33:48 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-19 01:33:48 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-19 01:33:48 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-19 01:33:48 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-19 01:33:48 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-19 01:33:48 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-19 01:33:48 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-19 01:33:48 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-19 01:33:52 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-19 01:33:52 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-19 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-19 01:33:52 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-19 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-19 01:33:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-19 01:33:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KxU_bIxxP7/ea_profile.json
* 2023-06-19 01:33:56 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KxU_bIxxP7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-19 01:33:56 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-20 01:33:29 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-20 01:33:30 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-20 01:33:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-20 01:33:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-20 01:33:30 (4089) [INFO] 
* 2023-06-20 01:33:30 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-20 01:33:30 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-20 01:33:30 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-20 01:33:30 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-20 01:33:30 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-20 01:33:30 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-20 01:33:30 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-20 01:33:30 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-20 01:33:30 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-20 01:33:30 (4119) [INFO] 
* 2023-06-20 01:33:30 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-20 01:33:30 (4089) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-20 01:33:45 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-20 01:33:45 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-20 01:33:45 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-20 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-20 01:33:45 (4102) [INFO] Trying other mirror.
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-20 01:33:45 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-20 01:33:45 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-20 01:33:45 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-20 01:33:45 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-20 01:33:45 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-20 01:33:45 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-20 01:33:45 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-20 01:33:45 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-20 01:33:45 (4102) [INFO]         or
* 2023-06-20 01:33:45 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-20 01:33:45 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-20 01:33:45 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-20 01:33:45 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-20 01:33:45 (4102) [INFO]         compromise:
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-20 01:33:45 (4102) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-20 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-20 01:33:45 (4119) [INFO] 
* 2023-06-20 01:33:45 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-20 01:33:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-20 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-20 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-20 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-20 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-20 01:33:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-20 01:33:46 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-20 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-20 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-20 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-20 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-20 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-20 01:33:49 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-20 01:33:49 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-20 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-20 01:33:49 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-20 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-20 01:33:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-20 01:33:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/43_OkxydB4/ea_profile.json
* 2023-06-20 01:33:53 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/43_OkxydB4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-20 01:33:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-21 01:34:22 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-21 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-21 01:34:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-21 01:34:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-21 01:34:23 (4089) [INFO] 
* 2023-06-21 01:34:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-21 01:34:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-21 01:34:23 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-21 01:34:23 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-21 01:34:23 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-21 01:34:23 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-21 01:34:23 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-21 01:34:23 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-21 01:34:23 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-21 01:34:23 (4119) [INFO] 
* 2023-06-21 01:34:23 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-21 01:34:23 (4089) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-21 01:34:37 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-21 01:34:37 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-21 01:34:37 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-21 01:34:37 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-21 01:34:37 (4102) [INFO] Trying other mirror.
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-21 01:34:37 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-21 01:34:37 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-21 01:34:37 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-21 01:34:37 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-21 01:34:37 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-21 01:34:37 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-21 01:34:37 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-21 01:34:37 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-21 01:34:37 (4102) [INFO]         or
* 2023-06-21 01:34:37 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-21 01:34:37 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-21 01:34:37 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-21 01:34:37 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-21 01:34:37 (4102) [INFO]         compromise:
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-21 01:34:37 (4102) [INFO] 
* 2023-06-21 01:34:37 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-21 01:34:37 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-21 01:34:38 (4119) [INFO] 
* 2023-06-21 01:34:38 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-21 01:34:38 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-21 01:34:38 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-21 01:34:39 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-21 01:34:39 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-21 01:34:39 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-21 01:34:39 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-21 01:34:39 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-21 01:34:39 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-21 01:34:39 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-21 01:34:39 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-21 01:34:39 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-21 01:34:39 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-21 01:34:43 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-21 01:34:43 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-21 01:34:43 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-21 01:34:43 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-21 01:34:44 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-21 01:34:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-21 01:34:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1WnexyJIou/ea_profile.json
* 2023-06-21 01:34:50 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1WnexyJIou/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-21 01:34:50 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-22 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-22 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-22 01:33:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-22 01:33:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-22 01:33:36 (4089) [INFO] 
* 2023-06-22 01:33:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-22 01:33:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-22 01:33:36 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-22 01:33:36 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-22 01:33:36 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-22 01:33:36 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-22 01:33:36 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-22 01:33:36 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-22 01:33:36 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-22 01:33:36 (4119) [INFO] 
* 2023-06-22 01:33:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-22 01:33:36 (4089) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-22 01:33:45 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-22 01:33:45 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-22 01:33:45 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-22 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-22 01:33:45 (4102) [INFO] Trying other mirror.
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-22 01:33:45 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-22 01:33:45 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-22 01:33:45 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-22 01:33:45 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-22 01:33:45 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-22 01:33:45 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-22 01:33:45 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-22 01:33:45 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-22 01:33:45 (4102) [INFO]         or
* 2023-06-22 01:33:45 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-22 01:33:45 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-22 01:33:45 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-22 01:33:45 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-22 01:33:45 (4102) [INFO]         compromise:
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-22 01:33:45 (4102) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-22 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-22 01:33:45 (4119) [INFO] 
* 2023-06-22 01:33:45 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-22 01:33:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-22 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-22 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-22 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-22 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-22 01:33:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-22 01:33:46 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-22 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-22 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-22 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-22 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-22 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-22 01:33:49 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-22 01:33:49 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-22 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-22 01:33:49 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-22 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-22 01:33:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-22 01:33:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ViswGyKU8Y/ea_profile.json
* 2023-06-22 01:33:54 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ViswGyKU8Y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-22 01:33:54 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-23 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-23 01:33:43 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-23 01:33:43 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-23 01:33:43 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-23 01:33:43 (4089) [INFO] 
* 2023-06-23 01:33:43 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-23 01:33:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-23 01:33:43 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-23 01:33:43 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-23 01:33:43 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-23 01:33:43 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-23 01:33:43 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-23 01:33:43 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-23 01:33:43 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-23 01:33:43 (4119) [INFO] 
* 2023-06-23 01:33:43 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-23 01:33:43 (4089) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-23 01:33:55 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-23 01:33:55 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-23 01:33:55 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-23 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-23 01:33:55 (4102) [INFO] Trying other mirror.
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-23 01:33:55 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-23 01:33:55 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-23 01:33:55 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-23 01:33:55 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-23 01:33:55 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-23 01:33:55 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-23 01:33:55 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-23 01:33:55 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-23 01:33:55 (4102) [INFO]         or
* 2023-06-23 01:33:55 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-23 01:33:55 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-23 01:33:55 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-23 01:33:55 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-23 01:33:55 (4102) [INFO]         compromise:
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-23 01:33:55 (4102) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-23 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-23 01:33:55 (4119) [INFO] 
* 2023-06-23 01:33:55 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-23 01:33:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-23 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-23 01:33:56 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-23 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-23 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-23 01:33:56 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-23 01:33:56 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-23 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-23 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-23 01:33:56 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-23 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-23 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-23 01:33:59 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-23 01:33:59 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-23 01:33:59 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-23 01:33:59 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-23 01:33:59 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-23 01:33:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-23 01:33:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wllXWYeS5x/ea_profile.json
* 2023-06-23 01:34:04 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wllXWYeS5x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-23 01:34:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-24 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-24 01:34:24 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-24 01:34:24 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-24 01:34:24 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-24 01:34:24 (4089) [INFO] 
* 2023-06-24 01:34:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-24 01:34:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-24 01:34:24 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-24 01:34:24 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-24 01:34:24 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-24 01:34:24 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-24 01:34:24 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-24 01:34:24 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-24 01:34:24 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-24 01:34:24 (4119) [INFO] 
* 2023-06-24 01:34:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-24 01:34:24 (4089) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-24 01:34:45 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-24 01:34:45 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-24 01:34:45 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-24 01:34:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-24 01:34:45 (4102) [INFO] Trying other mirror.
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-24 01:34:45 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-24 01:34:45 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-24 01:34:45 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-24 01:34:45 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-24 01:34:45 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-24 01:34:45 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-24 01:34:45 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-24 01:34:45 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-24 01:34:45 (4102) [INFO]         or
* 2023-06-24 01:34:45 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-24 01:34:45 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-24 01:34:45 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-24 01:34:45 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-24 01:34:45 (4102) [INFO]         compromise:
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-24 01:34:45 (4102) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-24 01:34:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-24 01:34:45 (4119) [INFO] 
* 2023-06-24 01:34:45 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-24 01:34:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-24 01:34:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-24 01:34:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-24 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-24 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-24 01:34:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-24 01:34:46 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-24 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-24 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-24 01:34:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-24 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-24 01:34:46 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-24 01:34:49 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-24 01:34:49 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-24 01:34:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-24 01:34:49 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-24 01:34:49 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-24 01:34:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-24 01:34:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VafUBklPB_/ea_profile.json
* 2023-06-24 01:34:54 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VafUBklPB_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-24 01:34:54 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-25 01:34:21 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-25 01:34:22 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-25 01:34:22 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-25 01:34:22 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-25 01:34:22 (4089) [INFO] 
* 2023-06-25 01:34:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-25 01:34:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-25 01:34:22 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-25 01:34:22 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-25 01:34:22 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-25 01:34:22 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-25 01:34:22 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-25 01:34:22 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-25 01:34:22 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-25 01:34:22 (4119) [INFO] 
* 2023-06-25 01:34:22 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-25 01:34:22 (4089) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-25 01:34:45 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-25 01:34:45 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-25 01:34:45 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-25 01:34:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-25 01:34:45 (4102) [INFO] Trying other mirror.
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-25 01:34:45 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-25 01:34:45 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-25 01:34:45 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-25 01:34:45 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-25 01:34:45 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-25 01:34:45 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-25 01:34:45 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-25 01:34:45 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-25 01:34:45 (4102) [INFO]         or
* 2023-06-25 01:34:45 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-25 01:34:45 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-25 01:34:45 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-25 01:34:45 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-25 01:34:45 (4102) [INFO]         compromise:
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-25 01:34:45 (4102) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-25 01:34:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-25 01:34:45 (4119) [INFO] 
* 2023-06-25 01:34:45 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-25 01:34:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-25 01:34:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-25 01:34:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-25 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-25 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-25 01:34:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-25 01:34:46 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-25 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-25 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-25 01:34:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-25 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-25 01:34:46 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-25 01:34:50 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-25 01:34:50 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-25 01:34:50 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-25 01:34:50 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-25 01:34:50 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-25 01:34:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-25 01:34:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uBPKkxXRPm/ea_profile.json
* 2023-06-25 01:34:55 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uBPKkxXRPm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-25 01:34:55 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-26 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-26 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-26 01:33:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-26 01:33:35 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-26 01:33:35 (4089) [INFO] 
* 2023-06-26 01:33:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-26 01:33:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-26 01:33:36 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-26 01:33:36 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-26 01:33:36 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-26 01:33:36 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-26 01:33:36 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-26 01:33:36 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-26 01:33:36 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-26 01:33:36 (4119) [INFO] 
* 2023-06-26 01:33:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-26 01:33:36 (4089) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-26 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-26 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-26 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-26 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-26 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-26 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-26 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-26 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-26 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-26 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-26 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-26 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-26 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-26 01:33:53 (4102) [INFO]         or
* 2023-06-26 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-26 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-26 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-26 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-26 01:33:53 (4102) [INFO]         compromise:
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-26 01:33:53 (4102) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-26 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-26 01:33:53 (4119) [INFO] 
* 2023-06-26 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-26 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-26 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-26 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-26 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-26 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-26 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-26 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-26 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-26 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-26 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-26 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-26 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-26 01:33:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-26 01:33:58 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-26 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-26 01:33:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-26 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-26 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-26 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PxfqQYUllX/ea_profile.json
* 2023-06-26 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PxfqQYUllX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-26 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-27 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-27 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-27 01:33:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-27 01:33:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-27 01:33:36 (4089) [INFO] 
* 2023-06-27 01:33:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-27 01:33:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-27 01:33:36 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-27 01:33:36 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-27 01:33:36 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-27 01:33:36 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-27 01:33:36 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-27 01:33:36 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-27 01:33:36 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-27 01:33:36 (4119) [INFO] 
* 2023-06-27 01:33:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-27 01:33:36 (4089) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-27 01:33:47 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-27 01:33:47 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-27 01:33:47 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-27 01:33:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-27 01:33:47 (4102) [INFO] Trying other mirror.
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-27 01:33:47 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-27 01:33:47 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-27 01:33:47 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-27 01:33:47 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-27 01:33:47 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-27 01:33:47 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-27 01:33:47 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-27 01:33:47 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-27 01:33:47 (4102) [INFO]         or
* 2023-06-27 01:33:47 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-27 01:33:47 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-27 01:33:47 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-27 01:33:47 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-27 01:33:47 (4102) [INFO]         compromise:
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-27 01:33:47 (4102) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-27 01:33:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-27 01:33:47 (4119) [INFO] 
* 2023-06-27 01:33:47 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-27 01:33:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-27 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-27 01:33:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-27 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-27 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-27 01:33:49 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-27 01:33:49 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-27 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-27 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-27 01:33:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-27 01:33:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-27 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-27 01:33:52 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-27 01:33:52 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-27 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-27 01:33:52 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-27 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-27 01:33:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-27 01:33:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gR_3g6_pN5/ea_profile.json
* 2023-06-27 01:33:58 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gR_3g6_pN5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-27 01:33:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-28 01:33:26 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-28 01:33:26 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-28 01:33:26 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-28 01:33:26 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-28 01:33:26 (4089) [INFO] 
* 2023-06-28 01:33:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-28 01:33:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-28 01:33:27 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-28 01:33:27 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-28 01:33:27 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-28 01:33:27 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-28 01:33:27 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-28 01:33:27 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-28 01:33:27 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-28 01:33:27 (4119) [INFO] 
* 2023-06-28 01:33:27 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-28 01:33:27 (4089) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-28 01:33:36 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-28 01:33:36 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-28 01:33:36 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-28 01:33:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-28 01:33:36 (4102) [INFO] Trying other mirror.
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-28 01:33:36 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-28 01:33:36 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-28 01:33:36 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-28 01:33:36 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-28 01:33:36 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-28 01:33:36 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-28 01:33:36 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-28 01:33:36 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-28 01:33:36 (4102) [INFO]         or
* 2023-06-28 01:33:36 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-28 01:33:36 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-28 01:33:36 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-28 01:33:36 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-28 01:33:36 (4102) [INFO]         compromise:
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-28 01:33:36 (4102) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-28 01:33:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-28 01:33:36 (4119) [INFO] 
* 2023-06-28 01:33:36 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-28 01:33:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-28 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-28 01:33:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-28 01:33:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-28 01:33:37 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-28 01:33:37 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-28 01:33:37 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-28 01:33:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-28 01:33:37 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-28 01:33:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-28 01:33:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-28 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-28 01:33:41 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-28 01:33:41 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-28 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-28 01:33:41 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-28 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-28 01:33:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-28 01:33:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j2CV192ZqM/ea_profile.json
* 2023-06-28 01:33:47 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j2CV192ZqM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-28 01:33:47 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-29 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-29 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-29 01:33:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-29 01:33:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-29 01:33:34 (4089) [INFO] 
* 2023-06-29 01:33:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-29 01:33:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-29 01:33:35 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-29 01:33:35 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-29 01:33:35 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-29 01:33:35 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-29 01:33:35 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-29 01:33:35 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-29 01:33:35 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-29 01:33:35 (4119) [INFO] 
* 2023-06-29 01:33:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-29 01:33:35 (4089) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-29 01:33:42 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-29 01:33:42 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-29 01:33:42 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-29 01:33:42 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-29 01:33:42 (4102) [INFO] Trying other mirror.
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-29 01:33:42 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-29 01:33:42 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-29 01:33:42 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-29 01:33:42 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-29 01:33:42 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-29 01:33:42 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-29 01:33:42 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-29 01:33:42 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-29 01:33:42 (4102) [INFO]         or
* 2023-06-29 01:33:42 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-29 01:33:42 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-29 01:33:42 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-29 01:33:42 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-29 01:33:42 (4102) [INFO]         compromise:
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-29 01:33:42 (4102) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-29 01:33:42 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-29 01:33:42 (4119) [INFO] 
* 2023-06-29 01:33:42 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-29 01:33:42 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-29 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-29 01:33:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-29 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-29 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-29 01:33:44 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-29 01:33:44 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-29 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-29 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-29 01:33:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-29 01:33:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-29 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-29 01:33:47 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-29 01:33:47 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-29 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-29 01:33:47 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-29 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-29 01:33:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-29 01:33:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EFP5ZNu4Kl/ea_profile.json
* 2023-06-29 01:33:51 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EFP5ZNu4Kl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-29 01:33:51 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-30 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-06-30 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-06-30 01:33:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-30 01:33:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-30 01:33:36 (4089) [INFO] 
* 2023-06-30 01:33:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-30 01:33:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-06-30 01:33:37 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-06-30 01:33:37 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-06-30 01:33:37 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-06-30 01:33:37 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-06-30 01:33:37 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-06-30 01:33:37 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-06-30 01:33:37 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-06-30 01:33:37 (4119) [INFO] 
* 2023-06-30 01:33:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-30 01:33:37 (4089) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-06-30 01:34:02 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-06-30 01:34:02 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-06-30 01:34:02 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-06-30 01:34:02 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-30 01:34:02 (4102) [INFO] Trying other mirror.
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-06-30 01:34:02 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-30 01:34:02 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-30 01:34:02 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-30 01:34:02 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-30 01:34:02 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-30 01:34:02 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-30 01:34:02 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-30 01:34:02 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-06-30 01:34:02 (4102) [INFO]         or
* 2023-06-30 01:34:02 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-30 01:34:02 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-30 01:34:02 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-30 01:34:02 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-30 01:34:02 (4102) [INFO]         compromise:
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-06-30 01:34:02 (4102) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-06-30 01:34:02 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-30 01:34:02 (4119) [INFO] 
* 2023-06-30 01:34:02 (4102) [INFO] Is this ok [y/N]: 
* 2023-06-30 01:34:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-30 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-30 01:34:05 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-06-30 01:34:05 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-06-30 01:34:05 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-06-30 01:34:05 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-06-30 01:34:05 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-06-30 01:34:05 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-06-30 01:34:05 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-06-30 01:34:05 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-06-30 01:34:05 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-06-30 01:34:05 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-06-30 01:34:09 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-30 01:34:09 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-06-30 01:34:09 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-30 01:34:09 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-06-30 01:34:09 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-06-30 01:34:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-30 01:34:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I4Vs_1Qckx/ea_profile.json
* 2023-06-30 01:34:13 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I4Vs_1Qckx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-30 01:34:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-01 01:34:49 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-01 01:34:49 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-01 01:34:49 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-01 01:34:49 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-01 01:34:49 (4089) [INFO] 
* 2023-07-01 01:34:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-01 01:34:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-01 01:34:50 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-01 01:34:50 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-01 01:34:50 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-01 01:34:50 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-01 01:34:50 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-01 01:34:50 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-01 01:34:50 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-01 01:34:50 (4119) [INFO] 
* 2023-07-01 01:34:50 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-01 01:34:50 (4089) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-01 01:35:00 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-01 01:35:00 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-01 01:35:00 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-01 01:35:00 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-01 01:35:00 (4102) [INFO] Trying other mirror.
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-01 01:35:00 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-01 01:35:00 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-01 01:35:00 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-01 01:35:00 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-01 01:35:00 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-01 01:35:00 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-01 01:35:00 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-01 01:35:00 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-01 01:35:00 (4102) [INFO]         or
* 2023-07-01 01:35:00 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-01 01:35:00 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-01 01:35:00 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-01 01:35:00 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-01 01:35:00 (4102) [INFO]         compromise:
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-01 01:35:00 (4102) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-01 01:35:00 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-01 01:35:00 (4119) [INFO] 
* 2023-07-01 01:35:00 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-01 01:35:00 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-01 01:35:00 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-01 01:35:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-01 01:35:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-01 01:35:03 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-01 01:35:03 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-01 01:35:03 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-01 01:35:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-01 01:35:03 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-01 01:35:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-01 01:35:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-01 01:35:03 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-01 01:35:07 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-01 01:35:07 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-01 01:35:07 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-01 01:35:07 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-01 01:35:07 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-01 01:35:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-01 01:35:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/88VdaWtcv9/ea_profile.json
* 2023-07-01 01:35:13 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/88VdaWtcv9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-01 01:35:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-02 01:34:24 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-02 01:34:24 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-02 01:34:24 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-02 01:34:24 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-02 01:34:24 (4089) [INFO] 
* 2023-07-02 01:34:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-02 01:34:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-02 01:34:24 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-02 01:34:24 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-02 01:34:24 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-02 01:34:24 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-02 01:34:24 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-02 01:34:24 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-02 01:34:24 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-02 01:34:24 (4119) [INFO] 
* 2023-07-02 01:34:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-02 01:34:24 (4089) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-02 01:34:47 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-02 01:34:47 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-02 01:34:47 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-02 01:34:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-02 01:34:47 (4102) [INFO] Trying other mirror.
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-02 01:34:47 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-02 01:34:47 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-02 01:34:47 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-02 01:34:47 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-02 01:34:47 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-02 01:34:47 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-02 01:34:47 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-02 01:34:47 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-02 01:34:47 (4102) [INFO]         or
* 2023-07-02 01:34:47 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-02 01:34:47 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-02 01:34:47 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-02 01:34:47 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-02 01:34:47 (4102) [INFO]         compromise:
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-02 01:34:47 (4102) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-02 01:34:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-02 01:34:47 (4119) [INFO] 
* 2023-07-02 01:34:47 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-02 01:34:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-02 01:34:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-02 01:34:48 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-02 01:34:48 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-02 01:34:48 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-02 01:34:48 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-02 01:34:48 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-02 01:34:48 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-02 01:34:48 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-02 01:34:48 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-02 01:34:48 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-02 01:34:48 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-02 01:34:51 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-02 01:34:51 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-02 01:34:51 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-02 01:34:51 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-02 01:34:51 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-02 01:34:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-02 01:34:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s6P8KoZZ8W/ea_profile.json
* 2023-07-02 01:34:55 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s6P8KoZZ8W/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-02 01:34:55 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-03 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-03 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-03 01:33:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-03 01:33:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-03 01:33:38 (4089) [INFO] 
* 2023-07-03 01:33:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-03 01:33:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-03 01:33:39 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-03 01:33:39 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-03 01:33:39 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-03 01:33:39 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-03 01:33:39 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-03 01:33:39 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-03 01:33:39 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-03 01:33:39 (4119) [INFO] 
* 2023-07-03 01:33:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-03 01:33:39 (4089) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-03 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-03 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-03 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-03 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-03 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-03 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-03 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-03 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-03 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-03 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-03 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-03 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-03 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-03 01:33:53 (4102) [INFO]         or
* 2023-07-03 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-03 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-03 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-03 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-03 01:33:53 (4102) [INFO]         compromise:
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-03 01:33:53 (4102) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-03 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-03 01:33:53 (4119) [INFO] 
* 2023-07-03 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-03 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-03 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-03 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-03 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-03 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-03 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-03 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-03 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-03 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-03 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-03 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-03 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-03 01:33:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-03 01:33:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-03 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-03 01:33:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-03 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-03 01:33:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-03 01:33:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Mic9O0akah/ea_profile.json
* 2023-07-03 01:34:01 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Mic9O0akah/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-03 01:34:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-04 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-04 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2023-07-04 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-04 01:33:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-04 01:33:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-04 01:33:45 (4089) [INFO] 
* 2023-07-04 01:33:45 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-04 01:33:45 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-04 01:33:45 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-04 01:33:45 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-04 01:33:45 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-04 01:33:45 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-04 01:33:45 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-04 01:33:45 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-04 01:33:45 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-04 01:33:45 (4119) [INFO] 
* 2023-07-04 01:33:45 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-04 01:33:45 (4089) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-04 01:34:03 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-04 01:34:03 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-04 01:34:03 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-04 01:34:03 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-04 01:34:03 (4102) [INFO] Trying other mirror.
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-04 01:34:03 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-04 01:34:03 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-04 01:34:03 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-04 01:34:03 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-04 01:34:03 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-04 01:34:03 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-04 01:34:03 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-04 01:34:03 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-04 01:34:03 (4102) [INFO]         or
* 2023-07-04 01:34:03 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-04 01:34:03 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-04 01:34:03 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-04 01:34:03 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-04 01:34:03 (4102) [INFO]         compromise:
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-04 01:34:03 (4102) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-04 01:34:03 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-04 01:34:03 (4119) [INFO] 
* 2023-07-04 01:34:03 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-04 01:34:03 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-04 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-04 01:34:04 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-04 01:34:04 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-04 01:34:04 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-04 01:34:04 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-04 01:34:04 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-04 01:34:04 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-04 01:34:04 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-04 01:34:04 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-04 01:34:04 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-04 01:34:04 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-04 01:34:07 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-04 01:34:07 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-04 01:34:07 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-04 01:34:07 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-04 01:34:07 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-04 01:34:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-04 01:34:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3Hcu2rgwy3/ea_profile.json
* 2023-07-04 01:34:14 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3Hcu2rgwy3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-04 01:34:14 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-05 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-05 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-05 01:33:46 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-05 01:33:46 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-05 01:33:46 (4089) [INFO] 
* 2023-07-05 01:33:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-05 01:33:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-05 01:33:47 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-05 01:33:47 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-05 01:33:47 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-05 01:33:47 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-05 01:33:47 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-05 01:33:47 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-05 01:33:47 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-05 01:33:47 (4119) [INFO] 
* 2023-07-05 01:33:47 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-05 01:33:47 (4089) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-05 01:33:59 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-05 01:33:59 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-05 01:33:59 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-05 01:33:59 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-05 01:33:59 (4102) [INFO] Trying other mirror.
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-05 01:33:59 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-05 01:33:59 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-05 01:33:59 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-05 01:33:59 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-05 01:33:59 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-05 01:33:59 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-05 01:33:59 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-05 01:33:59 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-05 01:33:59 (4102) [INFO]         or
* 2023-07-05 01:33:59 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-05 01:33:59 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-05 01:33:59 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-05 01:33:59 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-05 01:33:59 (4102) [INFO]         compromise:
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-05 01:33:59 (4102) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-05 01:33:59 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-05 01:33:59 (4119) [INFO] 
* 2023-07-05 01:33:59 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-05 01:33:59 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-05 01:33:59 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-05 01:34:00 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-05 01:34:00 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-05 01:34:00 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-05 01:34:00 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-05 01:34:00 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-05 01:34:00 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-05 01:34:00 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-05 01:34:00 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-05 01:34:00 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-05 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-05 01:34:03 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-05 01:34:03 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-05 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-05 01:34:03 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-05 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-05 01:34:03 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-05 01:34:03 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WJGWVjMQSi/ea_profile.json
* 2023-07-05 01:34:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WJGWVjMQSi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-05 01:34:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-06 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-06 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-06 01:33:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-06 01:33:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-06 01:33:41 (4089) [INFO] 
* 2023-07-06 01:33:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-06 01:33:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-06 01:33:41 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-06 01:33:41 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-06 01:33:41 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-06 01:33:41 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-06 01:33:41 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-06 01:33:41 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-06 01:33:41 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-06 01:33:41 (4119) [INFO] 
* 2023-07-06 01:33:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-06 01:33:41 (4089) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-06 01:33:51 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-06 01:33:51 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-06 01:33:51 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-06 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-06 01:33:51 (4102) [INFO] Trying other mirror.
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-06 01:33:51 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-06 01:33:51 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-06 01:33:51 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-06 01:33:51 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-06 01:33:51 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-06 01:33:51 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-06 01:33:51 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-06 01:33:51 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-06 01:33:51 (4102) [INFO]         or
* 2023-07-06 01:33:51 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-06 01:33:51 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-06 01:33:51 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-06 01:33:51 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-06 01:33:51 (4102) [INFO]         compromise:
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-06 01:33:51 (4102) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-06 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-06 01:33:51 (4119) [INFO] 
* 2023-07-06 01:33:51 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-06 01:33:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-06 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-06 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-06 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-06 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-06 01:33:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-06 01:33:52 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-06 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-06 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-06 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-06 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-06 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-06 01:33:55 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-06 01:33:55 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-06 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-06 01:33:55 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-06 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-06 01:33:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-06 01:33:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nNo04uZR9p/ea_profile.json
* 2023-07-06 01:33:59 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nNo04uZR9p/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-06 01:33:59 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-07 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-07 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-07 01:33:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-07 01:33:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-07 01:33:34 (4089) [INFO] 
* 2023-07-07 01:33:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-07 01:33:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-07 01:33:34 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-07 01:33:34 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-07 01:33:34 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-07 01:33:34 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-07 01:33:34 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-07 01:33:34 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-07 01:33:34 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-07 01:33:34 (4119) [INFO] 
* 2023-07-07 01:33:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-07 01:33:34 (4089) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-07 01:33:45 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-07 01:33:45 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-07 01:33:45 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-07 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-07 01:33:45 (4102) [INFO] Trying other mirror.
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-07 01:33:45 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-07 01:33:45 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-07 01:33:45 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-07 01:33:45 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-07 01:33:45 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-07 01:33:45 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-07 01:33:45 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-07 01:33:45 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-07 01:33:45 (4102) [INFO]         or
* 2023-07-07 01:33:45 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-07 01:33:45 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-07 01:33:45 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-07 01:33:45 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-07 01:33:45 (4102) [INFO]         compromise:
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-07 01:33:45 (4102) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-07 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-07 01:33:45 (4119) [INFO] 
* 2023-07-07 01:33:45 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-07 01:33:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-07 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-07 01:33:47 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-07 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-07 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-07 01:33:47 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-07 01:33:47 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-07 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-07 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-07 01:33:47 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-07 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-07 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-07 01:33:50 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-07 01:33:50 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-07 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-07 01:33:50 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-07 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-07 01:33:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-07 01:33:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/saxNduY9QA/ea_profile.json
* 2023-07-07 01:33:54 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/saxNduY9QA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-07 01:33:54 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-08 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-08 01:34:31 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-08 01:34:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-08 01:34:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-08 01:34:31 (4089) [INFO] 
* 2023-07-08 01:34:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-08 01:34:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-08 01:34:31 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-08 01:34:31 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-08 01:34:31 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-08 01:34:31 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-08 01:34:31 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-08 01:34:31 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-08 01:34:31 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-08 01:34:31 (4119) [INFO] 
* 2023-07-08 01:34:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-08 01:34:31 (4089) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-08 01:34:43 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-08 01:34:43 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-08 01:34:43 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-08 01:34:43 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-08 01:34:43 (4102) [INFO] Trying other mirror.
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-08 01:34:43 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-08 01:34:43 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-08 01:34:43 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-08 01:34:43 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-08 01:34:43 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-08 01:34:43 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-08 01:34:43 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-08 01:34:43 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-08 01:34:43 (4102) [INFO]         or
* 2023-07-08 01:34:43 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-08 01:34:43 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-08 01:34:43 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-08 01:34:43 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-08 01:34:43 (4102) [INFO]         compromise:
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-08 01:34:43 (4102) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-08 01:34:43 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-08 01:34:43 (4119) [INFO] 
* 2023-07-08 01:34:43 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-08 01:34:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-08 01:34:43 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-08 01:34:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-08 01:34:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-08 01:34:44 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-08 01:34:44 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-08 01:34:44 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-08 01:34:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-08 01:34:44 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-08 01:34:44 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-08 01:34:44 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-08 01:34:44 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-08 01:34:48 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-08 01:34:48 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-08 01:34:48 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-08 01:34:48 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-08 01:34:48 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-08 01:34:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-08 01:34:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ImMFNSYBGg/ea_profile.json
* 2023-07-08 01:34:53 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ImMFNSYBGg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-08 01:34:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-09 01:34:18 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-09 01:34:18 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-09 01:34:18 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-09 01:34:18 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-09 01:34:18 (4089) [INFO] 
* 2023-07-09 01:34:18 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-09 01:34:19 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-09 01:34:19 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-09 01:34:19 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-09 01:34:19 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-09 01:34:19 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-09 01:34:19 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-09 01:34:19 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-09 01:34:19 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-09 01:34:19 (4119) [INFO] 
* 2023-07-09 01:34:19 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-09 01:34:19 (4089) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-09 01:34:29 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-09 01:34:29 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-09 01:34:29 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-09 01:34:29 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-09 01:34:29 (4102) [INFO] Trying other mirror.
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-09 01:34:29 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-09 01:34:29 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-09 01:34:29 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-09 01:34:29 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-09 01:34:29 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-09 01:34:29 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-09 01:34:29 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-09 01:34:29 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-09 01:34:29 (4102) [INFO]         or
* 2023-07-09 01:34:29 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-09 01:34:29 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-09 01:34:29 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-09 01:34:29 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-09 01:34:29 (4102) [INFO]         compromise:
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-09 01:34:29 (4102) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-09 01:34:29 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-09 01:34:29 (4119) [INFO] 
* 2023-07-09 01:34:29 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-09 01:34:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-09 01:34:29 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-09 01:34:30 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-09 01:34:30 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-09 01:34:30 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-09 01:34:30 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-09 01:34:30 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-09 01:34:30 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-09 01:34:30 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-09 01:34:30 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-09 01:34:30 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-09 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-09 01:34:33 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-09 01:34:33 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-09 01:34:33 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-09 01:34:33 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-09 01:34:33 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-09 01:34:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-09 01:34:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/w8cNgxdhVo/ea_profile.json
* 2023-07-09 01:34:38 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/w8cNgxdhVo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-09 01:34:38 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-10 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-10 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-10 01:33:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-10 01:33:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-10 01:33:42 (4089) [INFO] 
* 2023-07-10 01:33:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-10 01:33:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-10 01:33:43 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-10 01:33:43 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-10 01:33:43 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-10 01:33:43 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-10 01:33:43 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-10 01:33:43 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-10 01:33:43 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-10 01:33:43 (4119) [INFO] 
* 2023-07-10 01:33:43 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-10 01:33:43 (4089) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-10 01:33:57 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-10 01:33:57 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-10 01:33:57 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-10 01:33:57 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-10 01:33:57 (4102) [INFO] Trying other mirror.
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-10 01:33:57 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-10 01:33:57 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-10 01:33:57 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-10 01:33:57 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-10 01:33:57 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-10 01:33:57 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-10 01:33:57 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-10 01:33:57 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-10 01:33:57 (4102) [INFO]         or
* 2023-07-10 01:33:57 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-10 01:33:57 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-10 01:33:57 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-10 01:33:57 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-10 01:33:57 (4102) [INFO]         compromise:
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-10 01:33:57 (4102) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-10 01:33:57 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-10 01:33:57 (4119) [INFO] 
* 2023-07-10 01:33:57 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-10 01:33:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-10 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-10 01:33:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-10 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-10 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-10 01:33:58 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-10 01:33:58 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-10 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-10 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-10 01:33:58 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-10 01:33:58 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-10 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-10 01:34:02 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-10 01:34:02 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-10 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-10 01:34:02 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-10 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-10 01:34:03 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-10 01:34:03 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uPRkvWXUQY/ea_profile.json
* 2023-07-10 01:34:07 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uPRkvWXUQY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-10 01:34:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-11 01:33:30 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-11 01:33:31 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-11 01:33:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-11 01:33:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-11 01:33:31 (4089) [INFO] 
* 2023-07-11 01:33:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-11 01:33:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-11 01:33:31 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-11 01:33:31 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-11 01:33:31 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-11 01:33:31 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-11 01:33:31 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-11 01:33:31 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-11 01:33:31 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-11 01:33:31 (4119) [INFO] 
* 2023-07-11 01:33:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-11 01:33:31 (4089) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-11 01:33:46 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-11 01:33:46 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-11 01:33:46 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-11 01:33:46 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-11 01:33:46 (4102) [INFO] Trying other mirror.
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-11 01:33:46 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-11 01:33:46 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-11 01:33:46 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-11 01:33:46 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-11 01:33:46 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-11 01:33:46 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-11 01:33:46 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-11 01:33:46 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-11 01:33:46 (4102) [INFO]         or
* 2023-07-11 01:33:46 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-11 01:33:46 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-11 01:33:46 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-11 01:33:46 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-11 01:33:46 (4102) [INFO]         compromise:
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-11 01:33:46 (4102) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-11 01:33:46 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-11 01:33:46 (4119) [INFO] 
* 2023-07-11 01:33:46 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-11 01:33:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-11 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-11 01:33:47 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-11 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-11 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-11 01:33:47 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-11 01:33:47 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-11 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-11 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-11 01:33:47 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-11 01:33:47 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-11 01:33:47 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-11 01:33:50 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-11 01:33:50 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-11 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-11 01:33:50 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-11 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-11 01:33:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-11 01:33:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lysySSXzx5/ea_profile.json
* 2023-07-11 01:33:56 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lysySSXzx5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-11 01:33:56 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-12 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-12 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-12 01:33:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-12 01:33:35 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-12 01:33:35 (4089) [INFO] 
* 2023-07-12 01:33:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-12 01:33:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-12 01:33:35 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-12 01:33:35 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-12 01:33:35 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-12 01:33:35 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-12 01:33:35 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-12 01:33:35 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-12 01:33:35 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-12 01:33:35 (4119) [INFO] 
* 2023-07-12 01:33:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-12 01:33:35 (4089) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-12 01:33:50 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-12 01:33:50 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-12 01:33:50 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-12 01:33:50 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-12 01:33:50 (4102) [INFO] Trying other mirror.
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-12 01:33:50 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-12 01:33:50 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-12 01:33:50 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-12 01:33:50 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-12 01:33:50 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-12 01:33:50 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-12 01:33:50 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-12 01:33:50 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-12 01:33:50 (4102) [INFO]         or
* 2023-07-12 01:33:50 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-12 01:33:50 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-12 01:33:50 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-12 01:33:50 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-12 01:33:50 (4102) [INFO]         compromise:
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-12 01:33:50 (4102) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-12 01:33:50 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-12 01:33:50 (4119) [INFO] 
* 2023-07-12 01:33:50 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-12 01:33:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-12 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-12 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-12 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-12 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-12 01:33:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-12 01:33:52 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-12 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-12 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-12 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-12 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-12 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-12 01:33:56 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-12 01:33:56 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-12 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-12 01:33:56 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-12 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-12 01:33:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-12 01:33:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DHvFlzyD7r/ea_profile.json
* 2023-07-12 01:34:02 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DHvFlzyD7r/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-12 01:34:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-13 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-13 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-13 01:33:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-13 01:33:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-13 01:33:40 (4089) [INFO] 
* 2023-07-13 01:33:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-13 01:33:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-13 01:33:40 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-13 01:33:40 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-13 01:33:40 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-13 01:33:40 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-13 01:33:40 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-13 01:33:40 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-13 01:33:40 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-13 01:33:40 (4119) [INFO] 
* 2023-07-13 01:33:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-13 01:33:40 (4089) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-13 01:34:01 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-13 01:34:01 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-13 01:34:01 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-13 01:34:01 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-13 01:34:01 (4102) [INFO] Trying other mirror.
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-13 01:34:01 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-13 01:34:01 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-13 01:34:01 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-13 01:34:01 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-13 01:34:01 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-13 01:34:01 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-13 01:34:01 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-13 01:34:01 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-13 01:34:01 (4102) [INFO]         or
* 2023-07-13 01:34:01 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-13 01:34:01 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-13 01:34:01 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-13 01:34:01 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-13 01:34:01 (4102) [INFO]         compromise:
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-13 01:34:01 (4102) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-13 01:34:01 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-13 01:34:01 (4119) [INFO] 
* 2023-07-13 01:34:01 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-13 01:34:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-13 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-13 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-13 01:34:02 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-13 01:34:02 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-13 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-13 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-13 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-13 01:34:09 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-13 01:34:09 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-13 01:34:09 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-13 01:34:09 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-13 01:34:09 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-13 01:34:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-13 01:34:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xMtdfprx9_/ea_profile.json
* 2023-07-13 01:34:15 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xMtdfprx9_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-13 01:34:15 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-14 01:34:31 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-14 01:34:32 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-14 01:34:32 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-14 01:34:32 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-14 01:34:32 (4089) [INFO] 
* 2023-07-14 01:34:32 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-14 01:34:32 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-14 01:34:32 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-14 01:34:32 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-14 01:34:32 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-14 01:34:32 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-14 01:34:32 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-14 01:34:32 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-14 01:34:32 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-14 01:34:32 (4119) [INFO] 
* 2023-07-14 01:34:32 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-14 01:34:32 (4089) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-14 01:34:51 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-14 01:34:51 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-14 01:34:51 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-14 01:34:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-14 01:34:51 (4102) [INFO] Trying other mirror.
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-14 01:34:51 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-14 01:34:51 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-14 01:34:51 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-14 01:34:51 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-14 01:34:51 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-14 01:34:51 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-14 01:34:51 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-14 01:34:51 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-14 01:34:51 (4102) [INFO]         or
* 2023-07-14 01:34:51 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-14 01:34:51 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-14 01:34:51 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-14 01:34:51 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-14 01:34:51 (4102) [INFO]         compromise:
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-14 01:34:51 (4102) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-14 01:34:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-14 01:34:51 (4119) [INFO] 
* 2023-07-14 01:34:51 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-14 01:34:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-14 01:34:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-14 01:34:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-14 01:34:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-14 01:34:52 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-14 01:34:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-14 01:34:52 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-14 01:34:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-14 01:34:52 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-14 01:34:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-14 01:34:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-14 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-14 01:34:54 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-14 01:34:54 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-14 01:34:54 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-14 01:34:54 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-14 01:34:54 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-14 01:34:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-14 01:34:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cC6lRdIQhA/ea_profile.json
* 2023-07-14 01:34:58 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cC6lRdIQhA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-14 01:34:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-15 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-15 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-15 01:34:16 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-15 01:34:16 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-15 01:34:16 (4089) [INFO] 
* 2023-07-15 01:34:16 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-15 01:34:17 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-15 01:34:17 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-15 01:34:17 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-15 01:34:17 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-15 01:34:17 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-15 01:34:17 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-15 01:34:17 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-15 01:34:17 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-15 01:34:17 (4119) [INFO] 
* 2023-07-15 01:34:17 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-15 01:34:17 (4089) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-15 01:34:30 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-15 01:34:30 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-15 01:34:30 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-15 01:34:30 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-15 01:34:30 (4102) [INFO] Trying other mirror.
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-15 01:34:30 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-15 01:34:30 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-15 01:34:30 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-15 01:34:30 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-15 01:34:30 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-15 01:34:30 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-15 01:34:30 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-15 01:34:30 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-15 01:34:30 (4102) [INFO]         or
* 2023-07-15 01:34:30 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-15 01:34:30 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-15 01:34:30 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-15 01:34:30 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-15 01:34:30 (4102) [INFO]         compromise:
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-15 01:34:30 (4102) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-15 01:34:30 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-15 01:34:30 (4119) [INFO] 
* 2023-07-15 01:34:30 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-15 01:34:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-15 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-15 01:34:31 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-15 01:34:31 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-15 01:34:31 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-15 01:34:31 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-15 01:34:31 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-15 01:34:31 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-15 01:34:31 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-15 01:34:31 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-15 01:34:31 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-15 01:34:31 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-15 01:34:35 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-15 01:34:35 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-15 01:34:35 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-15 01:34:35 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-15 01:34:35 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-15 01:34:35 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-15 01:34:35 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S9pFYzqLRp/ea_profile.json
* 2023-07-15 01:34:40 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S9pFYzqLRp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-15 01:34:40 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-16 01:34:20 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-16 01:34:21 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-16 01:34:21 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-16 01:34:21 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-16 01:34:21 (4089) [INFO] 
* 2023-07-16 01:34:21 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-16 01:34:21 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-16 01:34:21 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-16 01:34:21 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-16 01:34:21 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-16 01:34:21 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-16 01:34:21 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-16 01:34:21 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-16 01:34:21 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-16 01:34:21 (4119) [INFO] 
* 2023-07-16 01:34:21 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-16 01:34:21 (4089) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-16 01:34:33 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-16 01:34:33 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-16 01:34:33 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-16 01:34:33 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-16 01:34:33 (4102) [INFO] Trying other mirror.
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-16 01:34:33 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-16 01:34:33 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-16 01:34:33 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-16 01:34:33 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-16 01:34:33 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-16 01:34:33 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-16 01:34:33 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-16 01:34:33 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-16 01:34:33 (4102) [INFO]         or
* 2023-07-16 01:34:33 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-16 01:34:33 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-16 01:34:33 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-16 01:34:33 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-16 01:34:33 (4102) [INFO]         compromise:
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-16 01:34:33 (4102) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-16 01:34:33 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-16 01:34:33 (4119) [INFO] 
* 2023-07-16 01:34:33 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-16 01:34:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-16 01:34:33 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-16 01:34:35 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-16 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-16 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-16 01:34:35 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-16 01:34:35 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-16 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-16 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-16 01:34:35 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-16 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-16 01:34:35 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-16 01:34:39 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-16 01:34:39 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-16 01:34:39 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-16 01:34:39 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-16 01:34:39 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-16 01:34:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-16 01:34:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fwb7tt27j3/ea_profile.json
* 2023-07-16 01:34:46 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fwb7tt27j3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-16 01:34:46 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-17 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-17 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-17 01:33:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-17 01:33:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-17 01:33:37 (4089) [INFO] 
* 2023-07-17 01:33:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-17 01:33:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-17 01:33:38 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-17 01:33:38 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-17 01:33:38 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-17 01:33:38 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-17 01:33:38 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-17 01:33:38 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-17 01:33:38 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-17 01:33:38 (4119) [INFO] 
* 2023-07-17 01:33:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-17 01:33:38 (4089) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-17 01:33:55 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-17 01:33:55 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-17 01:33:55 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-17 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-17 01:33:55 (4102) [INFO] Trying other mirror.
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-17 01:33:55 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-17 01:33:55 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-17 01:33:55 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-17 01:33:55 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-17 01:33:55 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-17 01:33:55 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-17 01:33:55 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-17 01:33:55 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-17 01:33:55 (4102) [INFO]         or
* 2023-07-17 01:33:55 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-17 01:33:55 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-17 01:33:55 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-17 01:33:55 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-17 01:33:55 (4102) [INFO]         compromise:
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-17 01:33:55 (4102) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-17 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-17 01:33:55 (4119) [INFO] 
* 2023-07-17 01:33:55 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-17 01:33:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-17 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-17 01:33:56 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-17 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-17 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-17 01:33:56 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-17 01:33:56 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-17 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-17 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-17 01:33:56 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-17 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-17 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-17 01:34:00 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-17 01:34:00 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-17 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-17 01:34:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-17 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-17 01:34:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-17 01:34:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oKth5UEG5W/ea_profile.json
* 2023-07-17 01:34:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oKth5UEG5W/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-17 01:34:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-18 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-18 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-18 01:33:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-18 01:33:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-18 01:33:39 (4089) [INFO] 
* 2023-07-18 01:33:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-18 01:33:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-18 01:33:40 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-18 01:33:40 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-18 01:33:40 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-18 01:33:40 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-18 01:33:40 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-18 01:33:40 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-18 01:33:40 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-18 01:33:40 (4119) [INFO] 
* 2023-07-18 01:33:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-18 01:33:40 (4089) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-18 01:33:55 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-18 01:33:55 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-18 01:33:55 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-18 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-18 01:33:55 (4102) [INFO] Trying other mirror.
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-18 01:33:55 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-18 01:33:55 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-18 01:33:55 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-18 01:33:55 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-18 01:33:55 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-18 01:33:55 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-18 01:33:55 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-18 01:33:55 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-18 01:33:55 (4102) [INFO]         or
* 2023-07-18 01:33:55 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-18 01:33:55 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-18 01:33:55 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-18 01:33:55 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-18 01:33:55 (4102) [INFO]         compromise:
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-18 01:33:55 (4102) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-18 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-18 01:33:55 (4119) [INFO] 
* 2023-07-18 01:33:55 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-18 01:33:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-18 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-18 01:33:56 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-18 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-18 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-18 01:33:56 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-18 01:33:56 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-18 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-18 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-18 01:33:56 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-18 01:33:56 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-18 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-18 01:34:00 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-18 01:34:00 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-18 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-18 01:34:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-18 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-18 01:34:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-18 01:34:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mvmD2nOGIF/ea_profile.json
* 2023-07-18 01:34:05 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mvmD2nOGIF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-18 01:34:05 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-19 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-19 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-19 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-19 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-19 01:33:33 (4089) [INFO] 
* 2023-07-19 01:33:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-19 01:33:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-19 01:33:34 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-19 01:33:34 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-19 01:33:34 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-19 01:33:34 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-19 01:33:34 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-19 01:33:34 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-19 01:33:34 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-19 01:33:34 (4119) [INFO] 
* 2023-07-19 01:33:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-19 01:33:34 (4089) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-19 01:33:44 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-19 01:33:44 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-19 01:33:44 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-19 01:33:44 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-19 01:33:44 (4102) [INFO] Trying other mirror.
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-19 01:33:44 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-19 01:33:44 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-19 01:33:44 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-19 01:33:44 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-19 01:33:44 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-19 01:33:44 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-19 01:33:44 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-19 01:33:44 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-19 01:33:44 (4102) [INFO]         or
* 2023-07-19 01:33:44 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-19 01:33:44 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-19 01:33:44 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-19 01:33:44 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-19 01:33:44 (4102) [INFO]         compromise:
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-19 01:33:44 (4102) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-19 01:33:44 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-19 01:33:44 (4119) [INFO] 
* 2023-07-19 01:33:44 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-19 01:33:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-19 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-19 01:33:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-19 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-19 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-19 01:33:45 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-19 01:33:45 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-19 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-19 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-19 01:33:45 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-19 01:33:45 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-19 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-19 01:33:48 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-19 01:33:48 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-19 01:33:48 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-19 01:33:48 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-19 01:33:48 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-19 01:33:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-19 01:33:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p4DeCbs5EJ/ea_profile.json
* 2023-07-19 01:33:53 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p4DeCbs5EJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-19 01:33:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-20 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-20 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-20 01:33:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-20 01:33:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-20 01:33:39 (4089) [INFO] 
* 2023-07-20 01:33:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-20 01:33:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-20 01:33:39 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-20 01:33:39 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-20 01:33:39 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-20 01:33:39 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-20 01:33:39 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-20 01:33:39 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-20 01:33:39 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-20 01:33:39 (4119) [INFO] 
* 2023-07-20 01:33:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-20 01:33:39 (4089) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-20 01:33:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-20 01:33:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-20 01:33:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-20 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-20 01:33:52 (4102) [INFO] Trying other mirror.
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-20 01:33:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-20 01:33:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-20 01:33:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-20 01:33:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-20 01:33:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-20 01:33:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-20 01:33:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-20 01:33:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-20 01:33:52 (4102) [INFO]         or
* 2023-07-20 01:33:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-20 01:33:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-20 01:33:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-20 01:33:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-20 01:33:52 (4102) [INFO]         compromise:
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-20 01:33:52 (4102) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-20 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-20 01:33:52 (4119) [INFO] 
* 2023-07-20 01:33:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-20 01:33:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-20 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-20 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-20 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-20 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-20 01:33:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-20 01:33:53 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-20 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-20 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-20 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-20 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-20 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-20 01:33:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-20 01:33:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-20 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-20 01:33:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-20 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-20 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-20 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tPhKAK29Dv/ea_profile.json
* 2023-07-20 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tPhKAK29Dv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-20 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-21 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-21 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-21 01:33:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-21 01:33:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-21 01:33:40 (4089) [INFO] 
* 2023-07-21 01:33:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-21 01:33:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-21 01:33:40 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-21 01:33:40 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-21 01:33:40 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-21 01:33:40 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-21 01:33:40 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-21 01:33:40 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-21 01:33:40 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-21 01:33:40 (4119) [INFO] 
* 2023-07-21 01:33:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-21 01:33:40 (4089) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-21 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-21 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-21 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-21 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-21 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-21 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-21 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-21 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-21 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-21 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-21 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-21 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-21 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-21 01:33:53 (4102) [INFO]         or
* 2023-07-21 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-21 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-21 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-21 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-21 01:33:53 (4102) [INFO]         compromise:
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-21 01:33:53 (4102) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-21 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-21 01:33:53 (4119) [INFO] 
* 2023-07-21 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-21 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-21 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-21 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-21 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-21 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-21 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-21 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-21 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-21 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-21 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-21 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-21 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-21 01:33:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-21 01:33:58 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-21 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-21 01:33:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-21 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-21 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-21 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2V70chyVDo/ea_profile.json
* 2023-07-21 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2V70chyVDo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-21 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-22 01:34:33 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-22 01:34:34 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-22 01:34:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-22 01:34:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-22 01:34:34 (4089) [INFO] 
* 2023-07-22 01:34:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-22 01:34:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-22 01:34:34 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-22 01:34:34 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-22 01:34:34 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-22 01:34:34 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-22 01:34:34 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-22 01:34:34 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-22 01:34:34 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-22 01:34:34 (4119) [INFO] 
* 2023-07-22 01:34:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-22 01:34:34 (4089) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-22 01:34:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-22 01:34:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-22 01:34:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-22 01:34:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-22 01:34:52 (4102) [INFO] Trying other mirror.
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-22 01:34:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-22 01:34:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-22 01:34:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-22 01:34:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-22 01:34:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-22 01:34:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-22 01:34:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-22 01:34:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-22 01:34:52 (4102) [INFO]         or
* 2023-07-22 01:34:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-22 01:34:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-22 01:34:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-22 01:34:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-22 01:34:52 (4102) [INFO]         compromise:
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-22 01:34:52 (4102) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-22 01:34:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-22 01:34:52 (4119) [INFO] 
* 2023-07-22 01:34:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-22 01:34:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-22 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-22 01:34:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-22 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-22 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-22 01:34:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-22 01:34:53 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-22 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-22 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-22 01:34:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-22 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-22 01:34:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-22 01:35:00 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-22 01:35:00 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-22 01:35:00 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-22 01:35:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-22 01:35:00 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-22 01:35:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-22 01:35:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vOemYIgOvQ/ea_profile.json
* 2023-07-22 01:35:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vOemYIgOvQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-22 01:35:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-23 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-23 01:34:24 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-23 01:34:24 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-23 01:34:24 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-23 01:34:24 (4089) [INFO] 
* 2023-07-23 01:34:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-23 01:34:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-23 01:34:24 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-23 01:34:24 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-23 01:34:24 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-23 01:34:24 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-23 01:34:24 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-23 01:34:24 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-23 01:34:24 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-23 01:34:24 (4119) [INFO] 
* 2023-07-23 01:34:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-23 01:34:24 (4089) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-23 01:34:37 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-23 01:34:37 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-23 01:34:37 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-23 01:34:37 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-23 01:34:37 (4102) [INFO] Trying other mirror.
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-23 01:34:37 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-23 01:34:37 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-23 01:34:37 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-23 01:34:37 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-23 01:34:37 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-23 01:34:37 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-23 01:34:37 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-23 01:34:37 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-23 01:34:37 (4102) [INFO]         or
* 2023-07-23 01:34:37 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-23 01:34:37 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-23 01:34:37 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-23 01:34:37 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-23 01:34:37 (4102) [INFO]         compromise:
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-23 01:34:37 (4102) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-23 01:34:37 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-23 01:34:37 (4119) [INFO] 
* 2023-07-23 01:34:37 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-23 01:34:37 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-23 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-23 01:34:38 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-23 01:34:38 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-23 01:34:38 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-23 01:34:38 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-23 01:34:38 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-23 01:34:38 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-23 01:34:38 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-23 01:34:38 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-23 01:34:38 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-23 01:34:38 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-23 01:34:42 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-23 01:34:42 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-23 01:34:42 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-23 01:34:42 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-23 01:34:42 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-23 01:34:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-23 01:34:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QZFqIvUCAX/ea_profile.json
* 2023-07-23 01:34:46 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QZFqIvUCAX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-23 01:34:46 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-24 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-24 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-24 01:33:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-24 01:33:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-24 01:33:39 (4089) [INFO] 
* 2023-07-24 01:33:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-24 01:33:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-24 01:33:39 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-24 01:33:39 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-24 01:33:39 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-24 01:33:39 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-24 01:33:39 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-24 01:33:39 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-24 01:33:39 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-24 01:33:39 (4119) [INFO] 
* 2023-07-24 01:33:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-24 01:33:39 (4089) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-24 01:33:56 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-24 01:33:56 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-24 01:33:56 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-24 01:33:56 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-24 01:33:56 (4102) [INFO] Trying other mirror.
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-24 01:33:56 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-24 01:33:56 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-24 01:33:56 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-24 01:33:56 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-24 01:33:56 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-24 01:33:56 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-24 01:33:56 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-24 01:33:56 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-24 01:33:56 (4102) [INFO]         or
* 2023-07-24 01:33:56 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-24 01:33:56 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-24 01:33:56 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-24 01:33:56 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-24 01:33:56 (4102) [INFO]         compromise:
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-24 01:33:56 (4102) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-24 01:33:56 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-24 01:33:56 (4119) [INFO] 
* 2023-07-24 01:33:56 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-24 01:33:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-24 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-24 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-24 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-24 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-24 01:33:57 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-24 01:33:57 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-24 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-24 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-24 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-24 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-24 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-24 01:34:01 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-24 01:34:01 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-24 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-24 01:34:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-24 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-24 01:34:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-24 01:34:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ME_SSruvku/ea_profile.json
* 2023-07-24 01:34:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ME_SSruvku/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-24 01:34:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-25 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-25 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-25 01:33:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-25 01:33:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-25 01:33:38 (4089) [INFO] 
* 2023-07-25 01:33:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-25 01:33:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-25 01:33:39 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-25 01:33:39 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-25 01:33:39 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-25 01:33:39 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-25 01:33:39 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-25 01:33:39 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-25 01:33:39 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-25 01:33:39 (4119) [INFO] 
* 2023-07-25 01:33:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-25 01:33:39 (4089) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-25 01:33:49 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-25 01:33:49 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-25 01:33:49 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-25 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-25 01:33:49 (4102) [INFO] Trying other mirror.
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-25 01:33:49 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-25 01:33:49 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-25 01:33:49 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-25 01:33:49 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-25 01:33:49 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-25 01:33:49 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-25 01:33:49 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-25 01:33:49 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-25 01:33:49 (4102) [INFO]         or
* 2023-07-25 01:33:49 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-25 01:33:49 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-25 01:33:49 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-25 01:33:49 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-25 01:33:49 (4102) [INFO]         compromise:
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-25 01:33:49 (4102) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-25 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-25 01:33:49 (4119) [INFO] 
* 2023-07-25 01:33:49 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-25 01:33:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-25 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-25 01:33:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-25 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-25 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-25 01:33:50 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-25 01:33:50 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-25 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-25 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-25 01:33:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-25 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-25 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-25 01:33:54 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-25 01:33:54 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-25 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-25 01:33:54 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-25 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-25 01:33:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-25 01:33:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dGbWqqONPA/ea_profile.json
* 2023-07-25 01:33:59 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dGbWqqONPA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-25 01:33:59 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-26 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-26 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-26 01:33:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-26 01:33:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-26 01:33:45 (4089) [INFO] 
* 2023-07-26 01:33:45 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-26 01:33:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-26 01:33:46 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-26 01:33:46 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-26 01:33:46 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-26 01:33:46 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-26 01:33:46 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-26 01:33:46 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-26 01:33:46 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-26 01:33:46 (4119) [INFO] 
* 2023-07-26 01:33:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-26 01:33:46 (4089) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-26 01:34:02 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-26 01:34:02 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-26 01:34:02 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-26 01:34:02 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-26 01:34:02 (4102) [INFO] Trying other mirror.
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-26 01:34:02 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-26 01:34:02 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-26 01:34:02 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-26 01:34:02 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-26 01:34:02 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-26 01:34:02 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-26 01:34:02 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-26 01:34:02 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-26 01:34:02 (4102) [INFO]         or
* 2023-07-26 01:34:02 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-26 01:34:02 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-26 01:34:02 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-26 01:34:02 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-26 01:34:02 (4102) [INFO]         compromise:
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-26 01:34:02 (4102) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-26 01:34:02 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-26 01:34:02 (4119) [INFO] 
* 2023-07-26 01:34:02 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-26 01:34:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-26 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-26 01:34:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-26 01:34:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-26 01:34:03 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-26 01:34:03 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-26 01:34:03 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-26 01:34:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-26 01:34:03 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-26 01:34:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-26 01:34:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-26 01:34:03 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-26 01:34:11 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-26 01:34:11 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-26 01:34:11 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-26 01:34:11 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-26 01:34:11 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-26 01:34:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-26 01:34:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W_cHAV8Aog/ea_profile.json
* 2023-07-26 01:34:17 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W_cHAV8Aog/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-26 01:34:17 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-27 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-27 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-27 01:33:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-27 01:33:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-27 01:33:38 (4089) [INFO] 
* 2023-07-27 01:33:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-27 01:33:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-27 01:33:39 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-27 01:33:39 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-27 01:33:39 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-27 01:33:39 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-27 01:33:39 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-27 01:33:39 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-27 01:33:39 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-27 01:33:39 (4119) [INFO] 
* 2023-07-27 01:33:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-27 01:33:39 (4089) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-27 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-27 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-27 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-27 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-27 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-27 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-27 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-27 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-27 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-27 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-27 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-27 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-27 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-27 01:33:53 (4102) [INFO]         or
* 2023-07-27 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-27 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-27 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-27 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-27 01:33:53 (4102) [INFO]         compromise:
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-27 01:33:53 (4102) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-27 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-27 01:33:53 (4119) [INFO] 
* 2023-07-27 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-27 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-27 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-27 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-27 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-27 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-27 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-27 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-27 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-27 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-27 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-27 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-27 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-27 01:33:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-27 01:33:58 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-27 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-27 01:33:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-27 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-27 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-27 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JKVnHsRQ1V/ea_profile.json
* 2023-07-27 01:34:04 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JKVnHsRQ1V/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-27 01:34:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-28 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-28 01:33:43 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-28 01:33:43 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-28 01:33:43 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-28 01:33:43 (4089) [INFO] 
* 2023-07-28 01:33:43 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-28 01:33:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-28 01:33:43 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-28 01:33:43 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-28 01:33:43 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-28 01:33:43 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-28 01:33:43 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-28 01:33:43 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-28 01:33:43 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-28 01:33:43 (4119) [INFO] 
* 2023-07-28 01:33:43 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-28 01:33:43 (4089) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-28 01:34:01 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-28 01:34:01 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-28 01:34:01 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-28 01:34:01 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-28 01:34:01 (4102) [INFO] Trying other mirror.
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-28 01:34:01 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-28 01:34:01 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-28 01:34:01 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-28 01:34:01 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-28 01:34:01 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-28 01:34:01 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-28 01:34:01 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-28 01:34:01 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-28 01:34:01 (4102) [INFO]         or
* 2023-07-28 01:34:01 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-28 01:34:01 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-28 01:34:01 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-28 01:34:01 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-28 01:34:01 (4102) [INFO]         compromise:
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-28 01:34:01 (4102) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-28 01:34:01 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-28 01:34:01 (4119) [INFO] 
* 2023-07-28 01:34:01 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-28 01:34:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-28 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-28 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-28 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-28 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-28 01:34:02 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-28 01:34:02 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-28 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-28 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-28 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-28 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-28 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-28 01:34:08 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-28 01:34:08 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-28 01:34:08 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-28 01:34:08 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-28 01:34:08 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-28 01:34:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-28 01:34:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X5dEvbhqGM/ea_profile.json
* 2023-07-28 01:34:14 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X5dEvbhqGM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-28 01:34:14 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-29 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-29 01:34:24 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-29 01:34:24 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-29 01:34:24 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-29 01:34:24 (4089) [INFO] 
* 2023-07-29 01:34:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-29 01:34:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-29 01:34:24 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-29 01:34:24 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-29 01:34:24 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-29 01:34:24 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-29 01:34:24 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-29 01:34:24 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-29 01:34:24 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-29 01:34:24 (4119) [INFO] 
* 2023-07-29 01:34:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-29 01:34:24 (4089) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-29 01:34:32 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-29 01:34:32 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-29 01:34:32 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-29 01:34:32 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-29 01:34:32 (4102) [INFO] Trying other mirror.
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-29 01:34:32 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-29 01:34:32 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-29 01:34:32 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-29 01:34:32 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-29 01:34:32 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-29 01:34:32 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-29 01:34:32 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-29 01:34:32 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-29 01:34:32 (4102) [INFO]         or
* 2023-07-29 01:34:32 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-29 01:34:32 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-29 01:34:32 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-29 01:34:32 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-29 01:34:32 (4102) [INFO]         compromise:
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-29 01:34:32 (4102) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-29 01:34:32 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-29 01:34:32 (4119) [INFO] 
* 2023-07-29 01:34:32 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-29 01:34:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-29 01:34:32 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-29 01:34:34 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-29 01:34:34 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-29 01:34:34 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-29 01:34:34 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-29 01:34:34 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-29 01:34:34 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-29 01:34:34 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-29 01:34:34 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-29 01:34:34 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-29 01:34:34 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-29 01:34:36 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-29 01:34:36 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-29 01:34:36 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-29 01:34:36 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-29 01:34:36 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-29 01:34:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-29 01:34:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bsnoqGAGPu/ea_profile.json
* 2023-07-29 01:34:41 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bsnoqGAGPu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-29 01:34:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-30 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-30 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-30 01:34:16 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-30 01:34:16 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-30 01:34:16 (4089) [INFO] 
* 2023-07-30 01:34:17 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-30 01:34:17 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-30 01:34:17 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-30 01:34:17 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-30 01:34:17 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-30 01:34:17 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-30 01:34:17 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-30 01:34:17 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-30 01:34:17 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-30 01:34:17 (4119) [INFO] 
* 2023-07-30 01:34:17 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-30 01:34:17 (4089) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-30 01:34:36 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-30 01:34:36 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-30 01:34:36 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-30 01:34:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-30 01:34:36 (4102) [INFO] Trying other mirror.
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-30 01:34:36 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-30 01:34:36 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-30 01:34:36 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-30 01:34:36 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-30 01:34:36 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-30 01:34:36 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-30 01:34:36 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-30 01:34:36 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-30 01:34:36 (4102) [INFO]         or
* 2023-07-30 01:34:36 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-30 01:34:36 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-30 01:34:36 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-30 01:34:36 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-30 01:34:36 (4102) [INFO]         compromise:
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-30 01:34:36 (4102) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-30 01:34:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-30 01:34:36 (4119) [INFO] 
* 2023-07-30 01:34:36 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-30 01:34:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-30 01:34:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-30 01:34:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-30 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-30 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-30 01:34:37 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-30 01:34:37 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-30 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-30 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-30 01:34:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-30 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-30 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-30 01:34:42 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-30 01:34:42 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-30 01:34:42 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-30 01:34:42 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-30 01:34:42 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-30 01:34:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-30 01:34:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YVvNweH7YJ/ea_profile.json
* 2023-07-30 01:34:48 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YVvNweH7YJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-30 01:34:48 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-31 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-07-31 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-07-31 01:33:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-31 01:33:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-31 01:33:42 (4089) [INFO] 
* 2023-07-31 01:33:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-31 01:33:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-07-31 01:33:42 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-07-31 01:33:42 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-07-31 01:33:42 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-07-31 01:33:42 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-07-31 01:33:42 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-07-31 01:33:42 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-07-31 01:33:42 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-07-31 01:33:42 (4119) [INFO] 
* 2023-07-31 01:33:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-31 01:33:42 (4089) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-07-31 01:33:56 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-07-31 01:33:56 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-07-31 01:33:56 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-07-31 01:33:56 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-31 01:33:56 (4102) [INFO] Trying other mirror.
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-07-31 01:33:56 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-31 01:33:56 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-31 01:33:56 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-31 01:33:56 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-31 01:33:56 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-31 01:33:56 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-31 01:33:56 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-31 01:33:56 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-07-31 01:33:56 (4102) [INFO]         or
* 2023-07-31 01:33:56 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-31 01:33:56 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-31 01:33:56 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-31 01:33:56 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-31 01:33:56 (4102) [INFO]         compromise:
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-07-31 01:33:56 (4102) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-07-31 01:33:56 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-31 01:33:56 (4119) [INFO] 
* 2023-07-31 01:33:56 (4102) [INFO] Is this ok [y/N]: 
* 2023-07-31 01:33:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-31 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-31 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-07-31 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-07-31 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-07-31 01:33:57 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-07-31 01:33:57 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-07-31 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-07-31 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-07-31 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-07-31 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-07-31 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-07-31 01:34:01 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-31 01:34:01 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-07-31 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-31 01:34:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-07-31 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-07-31 01:34:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-31 01:34:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VmP8BgSjbS/ea_profile.json
* 2023-07-31 01:34:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VmP8BgSjbS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-07-31 01:34:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-01 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-01 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-01 01:34:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-01 01:34:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-01 01:34:30 (4089) [INFO] 
* 2023-08-01 01:34:30 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-01 01:34:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-01 01:34:31 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-01 01:34:31 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-01 01:34:31 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-01 01:34:31 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-01 01:34:31 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-01 01:34:31 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-01 01:34:31 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-01 01:34:31 (4119) [INFO] 
* 2023-08-01 01:34:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-01 01:34:31 (4089) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-01 01:34:54 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-01 01:34:54 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-01 01:34:54 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-01 01:34:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-01 01:34:54 (4102) [INFO] Trying other mirror.
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-01 01:34:54 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-01 01:34:54 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-01 01:34:54 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-01 01:34:54 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-01 01:34:54 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-01 01:34:54 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-01 01:34:54 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-01 01:34:54 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-01 01:34:54 (4102) [INFO]         or
* 2023-08-01 01:34:54 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-01 01:34:54 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-01 01:34:54 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-01 01:34:54 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-01 01:34:54 (4102) [INFO]         compromise:
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-01 01:34:54 (4102) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-01 01:34:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-01 01:34:54 (4119) [INFO] 
* 2023-08-01 01:34:54 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-01 01:34:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-01 01:34:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-01 01:34:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-01 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-01 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-01 01:34:55 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-01 01:34:55 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-01 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-01 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-01 01:34:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-01 01:34:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-01 01:34:55 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-01 01:35:01 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-01 01:35:01 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-01 01:35:01 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-01 01:35:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-01 01:35:01 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-01 01:35:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-01 01:35:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/okMTkEt1Xj/ea_profile.json
* 2023-08-01 01:35:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/okMTkEt1Xj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-01 01:35:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-02 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-02 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-02 01:33:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-02 01:33:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-02 01:33:40 (4089) [INFO] 
* 2023-08-02 01:33:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-02 01:33:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-02 01:33:41 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-02 01:33:41 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-02 01:33:41 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-02 01:33:41 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-02 01:33:41 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-02 01:33:41 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-02 01:33:41 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-02 01:33:41 (4119) [INFO] 
* 2023-08-02 01:33:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-02 01:33:41 (4089) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-02 01:33:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-02 01:33:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-02 01:33:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-02 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-02 01:33:52 (4102) [INFO] Trying other mirror.
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-02 01:33:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-02 01:33:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-02 01:33:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-02 01:33:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-02 01:33:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-02 01:33:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-02 01:33:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-02 01:33:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-02 01:33:52 (4102) [INFO]         or
* 2023-08-02 01:33:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-02 01:33:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-02 01:33:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-02 01:33:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-02 01:33:52 (4102) [INFO]         compromise:
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-02 01:33:52 (4102) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-02 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-02 01:33:52 (4119) [INFO] 
* 2023-08-02 01:33:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-02 01:33:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-02 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-02 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-02 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-02 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-02 01:33:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-02 01:33:53 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-02 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-02 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-02 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-02 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-02 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-02 01:34:02 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-02 01:34:02 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-02 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-02 01:34:02 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-02 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-02 01:34:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-02 01:34:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ADOvNkWJrz/ea_profile.json
* 2023-08-02 01:34:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ADOvNkWJrz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-02 01:34:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-03 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-03 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-03 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-03 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-03 01:33:33 (4089) [INFO] 
* 2023-08-03 01:33:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-03 01:33:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-03 01:33:33 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-03 01:33:33 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-03 01:33:33 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-03 01:33:33 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-03 01:33:33 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-03 01:33:33 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-03 01:33:33 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-03 01:33:33 (4119) [INFO] 
* 2023-08-03 01:33:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-03 01:33:33 (4089) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-03 01:33:56 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-03 01:33:56 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-03 01:33:56 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-03 01:33:56 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-03 01:33:56 (4102) [INFO] Trying other mirror.
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-03 01:33:56 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-03 01:33:56 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-03 01:33:56 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-03 01:33:56 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-03 01:33:56 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-03 01:33:56 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-03 01:33:56 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-03 01:33:56 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-03 01:33:56 (4102) [INFO]         or
* 2023-08-03 01:33:56 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-03 01:33:56 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-03 01:33:56 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-03 01:33:56 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-03 01:33:56 (4102) [INFO]         compromise:
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-03 01:33:56 (4102) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-03 01:33:56 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-03 01:33:56 (4119) [INFO] 
* 2023-08-03 01:33:56 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-03 01:33:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-03 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-03 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-03 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-03 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-03 01:33:57 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-03 01:33:57 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-03 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-03 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-03 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-03 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-03 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-03 01:34:01 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-03 01:34:01 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-03 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-03 01:34:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-03 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-03 01:34:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-03 01:34:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IpCQvY7Hgg/ea_profile.json
* 2023-08-03 01:34:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IpCQvY7Hgg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-03 01:34:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-04 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-04 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-04 01:33:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-04 01:33:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-04 01:33:34 (4089) [INFO] 
* 2023-08-04 01:33:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-04 01:33:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-04 01:33:35 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-04 01:33:35 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-04 01:33:35 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-04 01:33:35 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-04 01:33:35 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-04 01:33:35 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-04 01:33:35 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-04 01:33:35 (4119) [INFO] 
* 2023-08-04 01:33:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-04 01:33:35 (4089) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-04 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-04 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-04 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-04 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-04 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-04 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-04 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-04 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-04 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-04 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-04 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-04 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-04 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-04 01:33:53 (4102) [INFO]         or
* 2023-08-04 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-04 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-04 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-04 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-04 01:33:53 (4102) [INFO]         compromise:
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-04 01:33:53 (4102) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-04 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-04 01:33:53 (4119) [INFO] 
* 2023-08-04 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-04 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-04 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-04 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-04 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-04 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-04 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-04 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-04 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-04 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-04 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-04 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-04 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-04 01:33:59 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-04 01:33:59 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-04 01:33:59 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-04 01:33:59 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-04 01:33:59 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-04 01:33:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-04 01:33:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DicpZ2BZh0/ea_profile.json
* 2023-08-04 01:34:07 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DicpZ2BZh0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-04 01:34:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-05 01:34:20 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-05 01:34:21 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-05 01:34:21 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-05 01:34:21 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-05 01:34:21 (4089) [INFO] 
* 2023-08-05 01:34:21 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-05 01:34:21 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-05 01:34:21 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-05 01:34:21 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-05 01:34:21 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-05 01:34:21 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-05 01:34:21 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-05 01:34:21 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-05 01:34:21 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-05 01:34:21 (4119) [INFO] 
* 2023-08-05 01:34:21 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-05 01:34:21 (4089) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-05 01:34:32 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-05 01:34:32 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-05 01:34:32 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-05 01:34:32 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-05 01:34:32 (4102) [INFO] Trying other mirror.
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-05 01:34:32 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-05 01:34:32 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-05 01:34:32 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-05 01:34:32 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-05 01:34:32 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-05 01:34:32 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-05 01:34:32 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-05 01:34:32 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-05 01:34:32 (4102) [INFO]         or
* 2023-08-05 01:34:32 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-05 01:34:32 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-05 01:34:32 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-05 01:34:32 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-05 01:34:32 (4102) [INFO]         compromise:
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-05 01:34:32 (4102) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-05 01:34:32 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-05 01:34:32 (4119) [INFO] 
* 2023-08-05 01:34:32 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-05 01:34:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-05 01:34:32 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-05 01:34:33 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-05 01:34:33 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-05 01:34:33 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-05 01:34:33 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-05 01:34:33 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-05 01:34:33 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-05 01:34:33 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-05 01:34:33 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-05 01:34:33 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-05 01:34:33 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-05 01:34:37 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-05 01:34:37 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-05 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-05 01:34:37 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-05 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-05 01:34:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-05 01:34:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/P8WjUjwdyt/ea_profile.json
* 2023-08-05 01:34:41 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/P8WjUjwdyt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-05 01:34:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-06 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-06 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-06 01:34:00 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-06 01:34:00 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-06 01:34:00 (4089) [INFO] 
* 2023-08-06 01:34:00 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-06 01:34:01 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-06 01:34:01 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-06 01:34:01 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-06 01:34:01 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-06 01:34:01 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-06 01:34:01 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-06 01:34:01 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-06 01:34:01 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-06 01:34:01 (4119) [INFO] 
* 2023-08-06 01:34:01 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-06 01:34:01 (4089) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-06 01:34:11 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-06 01:34:11 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-06 01:34:11 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-06 01:34:11 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-06 01:34:11 (4102) [INFO] Trying other mirror.
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-06 01:34:11 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-06 01:34:11 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-06 01:34:11 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-06 01:34:11 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-06 01:34:11 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-06 01:34:11 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-06 01:34:11 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-06 01:34:11 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-06 01:34:11 (4102) [INFO]         or
* 2023-08-06 01:34:11 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-06 01:34:11 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-06 01:34:11 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-06 01:34:11 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-06 01:34:11 (4102) [INFO]         compromise:
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-06 01:34:11 (4102) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-06 01:34:11 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-06 01:34:11 (4119) [INFO] 
* 2023-08-06 01:34:11 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-06 01:34:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-06 01:34:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-06 01:34:12 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-06 01:34:12 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-06 01:34:12 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-06 01:34:12 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-06 01:34:12 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-06 01:34:12 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-06 01:34:12 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-06 01:34:12 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-06 01:34:12 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-06 01:34:12 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-06 01:34:19 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-06 01:34:19 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-06 01:34:19 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-06 01:34:19 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-06 01:34:19 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-06 01:34:19 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-06 01:34:19 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Upa1CNj9lD/ea_profile.json
* 2023-08-06 01:34:24 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Upa1CNj9lD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-06 01:34:24 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-07 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-07 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-07 01:33:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-07 01:33:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-07 01:33:40 (4089) [INFO] 
* 2023-08-07 01:33:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-07 01:33:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-07 01:33:41 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-07 01:33:41 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-07 01:33:41 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-07 01:33:41 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-07 01:33:41 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-07 01:33:41 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-07 01:33:41 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-07 01:33:41 (4119) [INFO] 
* 2023-08-07 01:33:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-07 01:33:41 (4089) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-07 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-07 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-07 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-07 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-07 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-07 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-07 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-07 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-07 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-07 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-07 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-07 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-07 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-07 01:33:53 (4102) [INFO]         or
* 2023-08-07 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-07 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-07 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-07 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-07 01:33:53 (4102) [INFO]         compromise:
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-07 01:33:53 (4102) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-07 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-07 01:33:53 (4119) [INFO] 
* 2023-08-07 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-07 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-07 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-07 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-07 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-07 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-07 01:33:55 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-07 01:33:55 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-07 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-07 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-07 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-07 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-07 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-07 01:33:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-07 01:33:58 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-07 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-07 01:33:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-07 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-07 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-07 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BJo8AMFxDb/ea_profile.json
* 2023-08-07 01:34:04 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BJo8AMFxDb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-07 01:34:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-08 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-08 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-08 01:33:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-08 01:33:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-08 01:33:36 (4089) [INFO] 
* 2023-08-08 01:33:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-08 01:33:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-08 01:33:36 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-08 01:33:36 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-08 01:33:36 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-08 01:33:36 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-08 01:33:36 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-08 01:33:36 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-08 01:33:36 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-08 01:33:36 (4119) [INFO] 
* 2023-08-08 01:33:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-08 01:33:36 (4089) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-08 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-08 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-08 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-08 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-08 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-08 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-08 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-08 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-08 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-08 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-08 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-08 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-08 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-08 01:33:53 (4102) [INFO]         or
* 2023-08-08 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-08 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-08 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-08 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-08 01:33:53 (4102) [INFO]         compromise:
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-08 01:33:53 (4102) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-08 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-08 01:33:53 (4119) [INFO] 
* 2023-08-08 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-08 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-08 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-08 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-08 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-08 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-08 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-08 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-08 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-08 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-08 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-08 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-08 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-08 01:33:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-08 01:33:58 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-08 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-08 01:33:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-08 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-08 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-08 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m_T382U9BH/ea_profile.json
* 2023-08-08 01:34:04 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m_T382U9BH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-08 01:34:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-09 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-09 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-09 01:33:46 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-09 01:33:46 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-09 01:33:46 (4089) [INFO] 
* 2023-08-09 01:33:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-09 01:33:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-09 01:33:47 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-09 01:33:47 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-09 01:33:47 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-09 01:33:47 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-09 01:33:47 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-09 01:33:47 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-09 01:33:47 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-09 01:33:47 (4119) [INFO] 
* 2023-08-09 01:33:47 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-09 01:33:47 (4089) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-09 01:33:58 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-09 01:33:58 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-09 01:33:58 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-09 01:33:58 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-09 01:33:58 (4102) [INFO] Trying other mirror.
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-09 01:33:58 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-09 01:33:58 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-09 01:33:58 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-09 01:33:58 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-09 01:33:58 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-09 01:33:58 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-09 01:33:58 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-09 01:33:58 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-09 01:33:58 (4102) [INFO]         or
* 2023-08-09 01:33:58 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-09 01:33:58 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-09 01:33:58 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-09 01:33:58 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-09 01:33:58 (4102) [INFO]         compromise:
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-09 01:33:58 (4102) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-09 01:33:58 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-09 01:33:58 (4119) [INFO] 
* 2023-08-09 01:33:58 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-09 01:33:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-09 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-09 01:33:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-09 01:33:59 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-09 01:33:59 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-09 01:33:59 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-09 01:33:59 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-09 01:33:59 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-09 01:33:59 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-09 01:33:59 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-09 01:33:59 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-09 01:33:59 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-09 01:34:09 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-09 01:34:09 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-09 01:34:09 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-09 01:34:09 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-09 01:34:09 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-09 01:34:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-09 01:34:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g7yMSwhLTX/ea_profile.json
* 2023-08-09 01:34:15 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g7yMSwhLTX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-09 01:34:15 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-10 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-10 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-10 01:33:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-10 01:33:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-10 01:33:37 (4089) [INFO] 
* 2023-08-10 01:33:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-10 01:33:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-10 01:33:37 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-10 01:33:37 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-10 01:33:37 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-10 01:33:37 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-10 01:33:37 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-10 01:33:37 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-10 01:33:38 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-10 01:33:38 (4119) [INFO] 
* 2023-08-10 01:33:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-10 01:33:38 (4089) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-10 01:33:54 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-10 01:33:54 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-10 01:33:54 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-10 01:33:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-10 01:33:54 (4102) [INFO] Trying other mirror.
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-10 01:33:54 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-10 01:33:54 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-10 01:33:54 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-10 01:33:54 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-10 01:33:54 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-10 01:33:54 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-10 01:33:54 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-10 01:33:54 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-10 01:33:54 (4102) [INFO]         or
* 2023-08-10 01:33:54 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-10 01:33:54 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-10 01:33:54 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-10 01:33:54 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-10 01:33:54 (4102) [INFO]         compromise:
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-10 01:33:54 (4102) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-10 01:33:54 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-10 01:33:54 (4119) [INFO] 
* 2023-08-10 01:33:54 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-10 01:33:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-10 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-10 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-10 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-10 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-10 01:33:55 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-10 01:33:55 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-10 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-10 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-10 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-10 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-10 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-10 01:33:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-10 01:33:58 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-10 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-10 01:33:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-10 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-10 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-10 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fMkcnduXwj/ea_profile.json
* 2023-08-10 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fMkcnduXwj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-10 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-11 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-11 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-11 01:33:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-11 01:33:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-11 01:33:37 (4089) [INFO] 
* 2023-08-11 01:33:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-11 01:33:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-11 01:33:37 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-11 01:33:37 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-11 01:33:37 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-11 01:33:37 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-11 01:33:37 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-11 01:33:37 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-11 01:33:37 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-11 01:33:37 (4119) [INFO] 
* 2023-08-11 01:33:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-11 01:33:37 (4089) [INFO] 
* 2023-08-11 01:34:20 (4102) [INFO] https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to repo.mongodb.org:443; Operation now in progress"
* 2023-08-11 01:34:20 (4102) [INFO] Trying other mirror.
* 2023-08-11 01:34:50 (4102) [INFO] https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to repo.mongodb.org:443; Operation now in progress"
* 2023-08-11 01:34:50 (4102) [INFO] Trying other mirror.
* 2023-08-11 01:35:20 (4102) [INFO] https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to repo.mongodb.org:443; Operation now in progress"
* 2023-08-11 01:35:20 (4102) [INFO] Trying other mirror.
* 2023-08-11 01:35:24 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-11 01:35:24 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-11 01:35:24 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-11 01:35:24 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-11 01:35:24 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-11 01:35:24 (4102) [INFO] Trying other mirror.
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-11 01:35:24 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-11 01:35:24 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-11 01:35:24 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-11 01:35:24 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-11 01:35:24 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-11 01:35:24 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-11 01:35:24 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-11 01:35:24 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-11 01:35:24 (4102) [INFO]         or
* 2023-08-11 01:35:24 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-11 01:35:24 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-11 01:35:24 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-11 01:35:24 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-11 01:35:24 (4102) [INFO]         compromise:
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-11 01:35:24 (4102) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-11 01:35:24 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-11 01:35:24 (4119) [INFO] 
* 2023-08-11 01:35:24 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-11 01:35:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-11 01:35:24 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-11 01:35:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-11 01:35:25 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-11 01:35:25 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-11 01:35:25 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-11 01:35:25 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-11 01:35:25 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-11 01:35:25 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-11 01:35:25 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-11 01:35:25 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-11 01:35:25 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-11 01:35:29 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-11 01:35:29 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-11 01:35:29 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-11 01:35:29 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-11 01:35:29 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-11 01:35:29 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-11 01:35:29 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hrJIQVYQLT/ea_profile.json
* 2023-08-11 01:35:37 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hrJIQVYQLT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-11 01:35:37 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-12 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-12 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-12 01:34:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-12 01:34:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-12 01:34:30 (4089) [INFO] 
* 2023-08-12 01:34:30 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-12 01:34:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-12 01:34:31 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-12 01:34:31 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-12 01:34:31 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-12 01:34:31 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-12 01:34:31 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-12 01:34:31 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-12 01:34:31 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-12 01:34:31 (4119) [INFO] 
* 2023-08-12 01:34:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-12 01:34:31 (4089) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-12 01:34:45 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-12 01:34:45 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-12 01:34:45 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-12 01:34:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-12 01:34:45 (4102) [INFO] Trying other mirror.
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-12 01:34:45 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-12 01:34:45 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-12 01:34:45 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-12 01:34:45 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-12 01:34:45 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-12 01:34:45 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-12 01:34:45 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-12 01:34:45 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-12 01:34:45 (4102) [INFO]         or
* 2023-08-12 01:34:45 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-12 01:34:45 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-12 01:34:45 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-12 01:34:45 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-12 01:34:45 (4102) [INFO]         compromise:
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-12 01:34:45 (4102) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-12 01:34:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-12 01:34:45 (4119) [INFO] 
* 2023-08-12 01:34:45 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-12 01:34:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-12 01:34:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-12 01:34:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-12 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-12 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-12 01:34:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-12 01:34:46 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-12 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-12 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-12 01:34:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-12 01:34:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-12 01:34:46 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-12 01:34:51 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-12 01:34:51 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-12 01:34:51 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-12 01:34:51 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-12 01:34:51 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-12 01:34:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-12 01:34:51 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oiks8jQNV3/ea_profile.json
* 2023-08-12 01:34:55 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oiks8jQNV3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-12 01:34:55 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-13 01:34:42 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-13 01:34:43 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-13 01:34:43 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-13 01:34:43 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-13 01:34:43 (4089) [INFO] 
* 2023-08-13 01:34:43 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-13 01:34:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-13 01:34:43 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-13 01:34:43 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-13 01:34:43 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-13 01:34:43 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-13 01:34:43 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-13 01:34:43 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-13 01:34:43 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-13 01:34:43 (4119) [INFO] 
* 2023-08-13 01:34:43 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-13 01:34:43 (4089) [INFO] 
* 2023-08-13 01:35:13 (4102) [INFO] http://centos.mirror.constant.com/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centos.mirror.constant.com:80; Operation now in progress"
* 2023-08-13 01:35:13 (4102) [INFO] Trying other mirror.
* 2023-08-13 01:35:17 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-13 01:35:17 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-13 01:35:17 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-13 01:35:17 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-13 01:35:17 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-13 01:35:17 (4102) [INFO] Trying other mirror.
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-13 01:35:17 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-13 01:35:17 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-13 01:35:17 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-13 01:35:17 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-13 01:35:17 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-13 01:35:17 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-13 01:35:17 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-13 01:35:17 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-13 01:35:17 (4102) [INFO]         or
* 2023-08-13 01:35:17 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-13 01:35:17 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-13 01:35:17 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-13 01:35:17 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-13 01:35:17 (4102) [INFO]         compromise:
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-13 01:35:17 (4102) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-13 01:35:17 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-13 01:35:17 (4119) [INFO] 
* 2023-08-13 01:35:17 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-13 01:35:17 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-13 01:35:17 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-13 01:35:18 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-13 01:35:18 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-13 01:35:18 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-13 01:35:18 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-13 01:35:18 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-13 01:35:18 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-13 01:35:18 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-13 01:35:18 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-13 01:35:18 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-13 01:35:18 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-13 01:35:44 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-13 01:35:44 (1567) [ERROR] http://centos.mirror.constant.com/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centos.mirror.constant.com:80; Operation now in progress"
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-13 01:35:44 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-13 01:35:44 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-13 01:35:44 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-13 01:35:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-13 01:35:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7vBndEhMhk/ea_profile.json
* 2023-08-13 01:35:50 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7vBndEhMhk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-13 01:35:50 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-14 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-14 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-14 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-14 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-14 01:33:33 (4089) [INFO] 
* 2023-08-14 01:33:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-14 01:33:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-14 01:33:33 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-14 01:33:33 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-14 01:33:33 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-14 01:33:33 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-14 01:33:33 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-14 01:33:33 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-14 01:33:33 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-14 01:33:33 (4119) [INFO] 
* 2023-08-14 01:33:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-14 01:33:33 (4089) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-14 01:33:49 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-14 01:33:49 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-14 01:33:49 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-14 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-14 01:33:49 (4102) [INFO] Trying other mirror.
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-14 01:33:49 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-14 01:33:49 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-14 01:33:49 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-14 01:33:49 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-14 01:33:49 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-14 01:33:49 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-14 01:33:49 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-14 01:33:49 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-14 01:33:49 (4102) [INFO]         or
* 2023-08-14 01:33:49 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-14 01:33:49 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-14 01:33:49 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-14 01:33:49 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-14 01:33:49 (4102) [INFO]         compromise:
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-14 01:33:49 (4102) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-14 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-14 01:33:49 (4119) [INFO] 
* 2023-08-14 01:33:49 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-14 01:33:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-14 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-14 01:33:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-14 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-14 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-14 01:33:50 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-14 01:33:50 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-14 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-14 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-14 01:33:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-14 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-14 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-14 01:34:00 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-14 01:34:00 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-14 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-14 01:34:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-14 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-14 01:34:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-14 01:34:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/odldxkkkMu/ea_profile.json
* 2023-08-14 01:34:36 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/odldxkkkMu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-14 01:34:36 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-15 01:37:03 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-15 01:37:03 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-15 01:37:03 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-15 01:37:03 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-15 01:37:03 (4089) [INFO] 
* 2023-08-15 01:37:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-15 01:37:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-15 01:37:04 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-15 01:37:04 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-15 01:37:04 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-15 01:37:04 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-15 01:37:04 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-15 01:37:04 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-15 01:37:04 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-15 01:37:04 (4119) [INFO] 
* 2023-08-15 01:37:04 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-15 01:37:04 (4089) [INFO] 
* 2023-08-15 01:37:43 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2023-08-15 01:37:43 (4102) [INFO] Trying other mirror.
* 2023-08-15 01:38:02 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-15 01:38:02 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-15 01:38:02 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-15 01:38:02 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-15 01:38:02 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-15 01:38:02 (4102) [INFO] Trying other mirror.
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-15 01:38:02 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-15 01:38:02 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-15 01:38:02 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-15 01:38:02 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-15 01:38:02 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-15 01:38:02 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-15 01:38:02 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-15 01:38:02 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-15 01:38:02 (4102) [INFO]         or
* 2023-08-15 01:38:02 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-15 01:38:02 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-15 01:38:02 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-15 01:38:02 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-15 01:38:02 (4102) [INFO]         compromise:
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-15 01:38:02 (4102) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-15 01:38:02 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-15 01:38:02 (4119) [INFO] 
* 2023-08-15 01:38:02 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-15 01:38:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-15 01:38:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-15 01:38:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-15 01:38:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-15 01:38:03 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-15 01:38:03 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-15 01:38:03 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-15 01:38:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-15 01:38:03 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-15 01:38:03 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-15 01:38:03 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-15 01:38:03 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-15 01:39:04 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-15 01:39:04 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-15 01:39:04 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-15 01:39:04 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-15 01:39:04 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-15 01:39:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-15 01:39:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9Yz1K0E0rR/ea_profile.json
* 2023-08-15 01:40:58 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9Yz1K0E0rR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-15 01:40:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-16 01:38:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-16 01:38:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-16 01:38:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-16 01:38:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-16 01:38:37 (4089) [INFO] 
* 2023-08-16 01:38:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-16 01:38:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-16 01:38:38 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-16 01:38:38 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-16 01:38:38 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-16 01:38:38 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-16 01:38:38 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-16 01:38:38 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-16 01:38:38 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-16 01:38:38 (4119) [INFO] 
* 2023-08-16 01:38:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-16 01:38:38 (4089) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-16 01:38:49 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-16 01:38:49 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-16 01:38:49 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-16 01:38:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-16 01:38:49 (4102) [INFO] Trying other mirror.
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-16 01:38:49 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-16 01:38:49 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-16 01:38:49 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-16 01:38:49 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-16 01:38:49 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-16 01:38:49 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-16 01:38:49 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-16 01:38:49 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-16 01:38:49 (4102) [INFO]         or
* 2023-08-16 01:38:49 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-16 01:38:49 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-16 01:38:49 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-16 01:38:49 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-16 01:38:49 (4102) [INFO]         compromise:
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-16 01:38:49 (4102) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-16 01:38:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-16 01:38:49 (4119) [INFO] 
* 2023-08-16 01:38:49 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-16 01:38:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-16 01:38:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-16 01:38:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-16 01:38:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-16 01:38:50 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-16 01:38:50 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-16 01:38:50 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-16 01:38:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-16 01:38:50 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-16 01:38:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-16 01:38:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-16 01:38:50 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-16 01:38:53 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-16 01:38:53 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-16 01:38:53 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-16 01:38:53 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-16 01:38:53 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-16 01:38:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-16 01:38:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZOUcVXJkzB/ea_profile.json
* 2023-08-16 01:38:58 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZOUcVXJkzB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-16 01:38:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-17 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-17 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-17 01:33:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-17 01:33:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-17 01:33:36 (4089) [INFO] 
* 2023-08-17 01:33:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-17 01:33:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-17 01:33:36 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-17 01:33:36 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-17 01:33:36 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-17 01:33:36 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-17 01:33:36 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-17 01:33:36 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-17 01:33:36 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-17 01:33:36 (4119) [INFO] 
* 2023-08-17 01:33:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-17 01:33:36 (4089) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO] http://linux.cc.lehigh.edu/centos/7.9.2009/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://linux.cc.lehigh.edu/centos/7.9.2009/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2023-08-17 01:34:16 (4102) [INFO] Trying other mirror.
* 2023-08-17 01:34:16 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-17 01:34:16 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-17 01:34:16 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-17 01:34:16 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-17 01:34:16 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-17 01:34:16 (4102) [INFO] Trying other mirror.
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-17 01:34:16 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-17 01:34:16 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-17 01:34:16 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-17 01:34:16 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-17 01:34:16 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-17 01:34:16 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-17 01:34:16 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-17 01:34:16 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-17 01:34:16 (4102) [INFO]         or
* 2023-08-17 01:34:16 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-17 01:34:16 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-17 01:34:16 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-17 01:34:16 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-17 01:34:16 (4102) [INFO]         compromise:
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-17 01:34:16 (4102) [INFO] 
* 2023-08-17 01:34:16 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-17 01:34:16 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-17 01:34:17 (4119) [INFO] 
* 2023-08-17 01:34:17 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-17 01:34:17 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-17 01:34:17 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-17 01:34:17 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-17 01:34:17 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-17 01:34:17 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-17 01:34:18 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-17 01:34:18 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-17 01:34:18 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-17 01:34:18 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-17 01:34:18 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-17 01:34:18 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-17 01:34:18 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-17 01:34:22 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-17 01:34:22 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-17 01:34:22 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-17 01:34:22 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-17 01:34:22 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-17 01:34:22 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-17 01:34:22 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MM_fCUCV5K/ea_profile.json
* 2023-08-17 01:34:28 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MM_fCUCV5K/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-17 01:34:28 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-18 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-18 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-18 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-18 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-18 01:33:33 (4089) [INFO] 
* 2023-08-18 01:33:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-18 01:33:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-18 01:33:34 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-18 01:33:34 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-18 01:33:34 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-18 01:33:34 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-18 01:33:34 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-18 01:33:34 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-18 01:33:34 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-18 01:33:34 (4119) [INFO] 
* 2023-08-18 01:33:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-18 01:33:34 (4089) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-18 01:33:51 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-18 01:33:51 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-18 01:33:51 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-18 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-18 01:33:51 (4102) [INFO] Trying other mirror.
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-18 01:33:51 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-18 01:33:51 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-18 01:33:51 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-18 01:33:51 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-18 01:33:51 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-18 01:33:51 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-18 01:33:51 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-18 01:33:51 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-18 01:33:51 (4102) [INFO]         or
* 2023-08-18 01:33:51 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-18 01:33:51 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-18 01:33:51 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-18 01:33:51 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-18 01:33:51 (4102) [INFO]         compromise:
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-18 01:33:51 (4102) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-18 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-18 01:33:51 (4119) [INFO] 
* 2023-08-18 01:33:51 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-18 01:33:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-18 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-18 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-18 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-18 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-18 01:33:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-18 01:33:52 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-18 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-18 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-18 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-18 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-18 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-18 01:33:56 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-18 01:33:56 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-18 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-18 01:33:56 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-18 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-18 01:33:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-18 01:33:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/psVYhbDp5d/ea_profile.json
* 2023-08-18 01:34:00 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/psVYhbDp5d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-18 01:34:00 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-19 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-19 01:34:30 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-19 01:34:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-19 01:34:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-19 01:34:30 (4089) [INFO] 
* 2023-08-19 01:34:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-19 01:34:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-19 01:34:31 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-19 01:34:31 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-19 01:34:31 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-19 01:34:31 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-19 01:34:31 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-19 01:34:31 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-19 01:34:31 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-19 01:34:31 (4119) [INFO] 
* 2023-08-19 01:34:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-19 01:34:31 (4089) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-19 01:34:48 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-19 01:34:48 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-19 01:34:48 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-19 01:34:48 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-19 01:34:48 (4102) [INFO] Trying other mirror.
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-19 01:34:48 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-19 01:34:48 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-19 01:34:48 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-19 01:34:48 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-19 01:34:48 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-19 01:34:48 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-19 01:34:48 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-19 01:34:48 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-19 01:34:48 (4102) [INFO]         or
* 2023-08-19 01:34:48 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-19 01:34:48 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-19 01:34:48 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-19 01:34:48 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-19 01:34:48 (4102) [INFO]         compromise:
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-19 01:34:48 (4102) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-19 01:34:48 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-19 01:34:48 (4119) [INFO] 
* 2023-08-19 01:34:48 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-19 01:34:48 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-19 01:34:48 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-19 01:34:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-19 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-19 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-19 01:34:49 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-19 01:34:49 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-19 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-19 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-19 01:34:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-19 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-19 01:34:49 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-19 01:34:55 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-19 01:34:55 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-19 01:34:55 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-19 01:34:55 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-19 01:34:55 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-19 01:34:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-19 01:34:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Wq0fO6K6YH/ea_profile.json
* 2023-08-19 01:34:59 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Wq0fO6K6YH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-19 01:34:59 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-20 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-20 01:34:17 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-20 01:34:17 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-20 01:34:17 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-20 01:34:17 (4089) [INFO] 
* 2023-08-20 01:34:17 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-20 01:34:17 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-20 01:34:17 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-20 01:34:17 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-20 01:34:17 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-20 01:34:17 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-20 01:34:17 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-20 01:34:17 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-20 01:34:17 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-20 01:34:17 (4119) [INFO] 
* 2023-08-20 01:34:17 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-20 01:34:17 (4089) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-20 01:34:25 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-20 01:34:25 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-20 01:34:25 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-20 01:34:25 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-20 01:34:25 (4102) [INFO] Trying other mirror.
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-20 01:34:25 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-20 01:34:25 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-20 01:34:25 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-20 01:34:25 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-20 01:34:25 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-20 01:34:25 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-20 01:34:25 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-20 01:34:25 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-20 01:34:25 (4102) [INFO]         or
* 2023-08-20 01:34:25 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-20 01:34:25 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-20 01:34:25 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-20 01:34:25 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-20 01:34:25 (4102) [INFO]         compromise:
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-20 01:34:25 (4102) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-20 01:34:25 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-20 01:34:25 (4119) [INFO] 
* 2023-08-20 01:34:25 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-20 01:34:25 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-20 01:34:25 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-20 01:34:26 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-20 01:34:26 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-20 01:34:26 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-20 01:34:26 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-20 01:34:26 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-20 01:34:26 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-20 01:34:26 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-20 01:34:26 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-20 01:34:26 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-20 01:34:26 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-20 01:34:29 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-20 01:34:29 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-20 01:34:29 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-20 01:34:29 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-20 01:34:29 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-20 01:34:30 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-20 01:34:30 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7hpNxlstnL/ea_profile.json
* 2023-08-20 01:34:34 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7hpNxlstnL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-20 01:34:34 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-21 01:33:43 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-21 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-21 01:33:44 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-21 01:33:44 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-21 01:33:44 (4089) [INFO] 
* 2023-08-21 01:33:44 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-21 01:33:44 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-21 01:33:44 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-21 01:33:44 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-21 01:33:44 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-21 01:33:44 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-21 01:33:44 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-21 01:33:44 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-21 01:33:44 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-21 01:33:44 (4119) [INFO] 
* 2023-08-21 01:33:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-21 01:33:44 (4089) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-21 01:34:01 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-21 01:34:01 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-21 01:34:01 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-21 01:34:01 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-21 01:34:01 (4102) [INFO] Trying other mirror.
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-21 01:34:01 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-21 01:34:01 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-21 01:34:01 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-21 01:34:01 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-21 01:34:01 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-21 01:34:01 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-21 01:34:01 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-21 01:34:01 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-21 01:34:01 (4102) [INFO]         or
* 2023-08-21 01:34:01 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-21 01:34:01 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-21 01:34:01 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-21 01:34:01 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-21 01:34:01 (4102) [INFO]         compromise:
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-21 01:34:01 (4102) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-21 01:34:01 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-21 01:34:01 (4119) [INFO] 
* 2023-08-21 01:34:01 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-21 01:34:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-21 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-21 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-21 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-21 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-21 01:34:02 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-21 01:34:02 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-21 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-21 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-21 01:34:02 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-21 01:34:02 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-21 01:34:02 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-21 01:34:05 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-21 01:34:05 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-21 01:34:05 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-21 01:34:05 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-21 01:34:05 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-21 01:34:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-21 01:34:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LyrPPZHoNj/ea_profile.json
* 2023-08-21 01:34:18 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LyrPPZHoNj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-21 01:34:18 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-22 01:34:58 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-22 01:34:59 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-22 01:34:59 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-22 01:34:59 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-22 01:34:59 (4089) [INFO] 
* 2023-08-22 01:35:00 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-22 01:35:00 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-22 01:35:00 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-22 01:35:00 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-22 01:35:00 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-22 01:35:00 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-22 01:35:00 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-22 01:35:00 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-22 01:35:00 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-22 01:35:00 (4119) [INFO] 
* 2023-08-22 01:35:00 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-22 01:35:00 (4089) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-22 01:35:13 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-22 01:35:13 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-22 01:35:13 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-22 01:35:13 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-22 01:35:13 (4102) [INFO] Trying other mirror.
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-22 01:35:13 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-22 01:35:13 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-22 01:35:13 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-22 01:35:13 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-22 01:35:13 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-22 01:35:13 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-22 01:35:13 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-22 01:35:13 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-22 01:35:13 (4102) [INFO]         or
* 2023-08-22 01:35:13 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-22 01:35:13 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-22 01:35:13 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-22 01:35:13 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-22 01:35:13 (4102) [INFO]         compromise:
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-22 01:35:13 (4102) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-22 01:35:13 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-22 01:35:13 (4119) [INFO] 
* 2023-08-22 01:35:13 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-22 01:35:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-22 01:35:13 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-22 01:35:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-22 01:35:15 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-22 01:35:15 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-22 01:35:15 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-22 01:35:15 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-22 01:35:15 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-22 01:35:15 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-22 01:35:15 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-22 01:35:15 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-22 01:35:15 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-22 01:35:49 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-22 01:35:49 (1567) [ERROR] http://repo.ialab.dsu.edu/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.ialab.dsu.edu/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-22 01:35:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-22 01:35:49 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-22 01:35:49 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-22 01:35:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-22 01:35:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NnSwurIK4A/ea_profile.json
* 2023-08-22 01:35:54 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NnSwurIK4A/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-22 01:35:54 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-23 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-23 01:33:34 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-23 01:33:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-23 01:33:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-23 01:33:34 (4089) [INFO] 
* 2023-08-23 01:33:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-23 01:33:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-23 01:33:35 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-23 01:33:35 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-23 01:33:35 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-23 01:33:35 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-23 01:33:35 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-23 01:33:35 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-23 01:33:35 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-23 01:33:35 (4119) [INFO] 
* 2023-08-23 01:33:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-23 01:33:35 (4089) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-23 01:33:49 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-23 01:33:49 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-23 01:33:49 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-23 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-23 01:33:49 (4102) [INFO] Trying other mirror.
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-23 01:33:49 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-23 01:33:49 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-23 01:33:49 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-23 01:33:49 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-23 01:33:49 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-23 01:33:49 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-23 01:33:49 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-23 01:33:49 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-23 01:33:49 (4102) [INFO]         or
* 2023-08-23 01:33:49 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-23 01:33:49 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-23 01:33:49 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-23 01:33:49 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-23 01:33:49 (4102) [INFO]         compromise:
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-23 01:33:49 (4102) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-23 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-23 01:33:49 (4119) [INFO] 
* 2023-08-23 01:33:49 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-23 01:33:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-23 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-23 01:33:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-23 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-23 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-23 01:33:50 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-23 01:33:50 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-23 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-23 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-23 01:33:50 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-23 01:33:50 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-23 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-23 01:33:54 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-23 01:33:54 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-23 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-23 01:33:54 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-23 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-23 01:33:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-23 01:33:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tGAXNtxx8n/ea_profile.json
* 2023-08-23 01:33:58 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tGAXNtxx8n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-23 01:33:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-24 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-24 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-24 01:33:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-24 01:33:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-24 01:33:42 (4089) [INFO] 
* 2023-08-24 01:33:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-24 01:33:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-24 01:33:42 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-24 01:33:42 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-24 01:33:42 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-24 01:33:42 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-24 01:33:42 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-24 01:33:42 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-24 01:33:42 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-24 01:33:42 (4119) [INFO] 
* 2023-08-24 01:33:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-24 01:33:42 (4089) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-24 01:33:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-24 01:33:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-24 01:33:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-24 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-24 01:33:52 (4102) [INFO] Trying other mirror.
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-24 01:33:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-24 01:33:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-24 01:33:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-24 01:33:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-24 01:33:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-24 01:33:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-24 01:33:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-24 01:33:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-24 01:33:52 (4102) [INFO]         or
* 2023-08-24 01:33:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-24 01:33:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-24 01:33:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-24 01:33:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-24 01:33:52 (4102) [INFO]         compromise:
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-24 01:33:52 (4102) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-24 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-24 01:33:52 (4119) [INFO] 
* 2023-08-24 01:33:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-24 01:33:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-24 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-24 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-24 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-24 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-24 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-24 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-24 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-24 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-24 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-24 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-24 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-24 01:33:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-24 01:33:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-24 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-24 01:33:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-24 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-24 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-24 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qQaWZixX44/ea_profile.json
* 2023-08-24 01:34:04 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qQaWZixX44/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-24 01:34:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-25 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-25 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-25 01:33:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-25 01:33:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-25 01:33:36 (4089) [INFO] 
* 2023-08-25 01:33:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-25 01:33:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-25 01:33:37 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-25 01:33:37 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-25 01:33:37 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-25 01:33:37 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-25 01:33:37 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-25 01:33:37 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-25 01:33:37 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-25 01:33:37 (4119) [INFO] 
* 2023-08-25 01:33:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-25 01:33:37 (4089) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-25 01:33:45 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-25 01:33:45 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-25 01:33:45 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-25 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-25 01:33:45 (4102) [INFO] Trying other mirror.
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-25 01:33:45 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-25 01:33:45 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-25 01:33:45 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-25 01:33:45 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-25 01:33:45 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-25 01:33:45 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-25 01:33:45 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-25 01:33:45 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-25 01:33:45 (4102) [INFO]         or
* 2023-08-25 01:33:45 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-25 01:33:45 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-25 01:33:45 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-25 01:33:45 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-25 01:33:45 (4102) [INFO]         compromise:
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-25 01:33:45 (4102) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-25 01:33:45 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-25 01:33:45 (4119) [INFO] 
* 2023-08-25 01:33:45 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-25 01:33:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-25 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-25 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-25 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-25 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-25 01:33:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-25 01:33:46 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-25 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-25 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-25 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-25 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-25 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-25 01:33:50 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-25 01:33:50 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-25 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-25 01:33:50 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-25 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-25 01:33:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-25 01:33:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2Qpb3u0Kds/ea_profile.json
* 2023-08-25 01:33:55 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2Qpb3u0Kds/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-25 01:33:55 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-26 01:34:22 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-26 01:34:23 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-26 01:34:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-26 01:34:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-26 01:34:23 (4089) [INFO] 
* 2023-08-26 01:34:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-26 01:34:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-26 01:34:23 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-26 01:34:23 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-26 01:34:23 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-26 01:34:23 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-26 01:34:23 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-26 01:34:23 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-26 01:34:23 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-26 01:34:23 (4119) [INFO] 
* 2023-08-26 01:34:23 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-26 01:34:23 (4089) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-26 01:34:36 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-26 01:34:36 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-26 01:34:36 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-26 01:34:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-26 01:34:36 (4102) [INFO] Trying other mirror.
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-26 01:34:36 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-26 01:34:36 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-26 01:34:36 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-26 01:34:36 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-26 01:34:36 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-26 01:34:36 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-26 01:34:36 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-26 01:34:36 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-26 01:34:36 (4102) [INFO]         or
* 2023-08-26 01:34:36 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-26 01:34:36 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-26 01:34:36 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-26 01:34:36 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-26 01:34:36 (4102) [INFO]         compromise:
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-26 01:34:36 (4102) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-26 01:34:36 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-26 01:34:36 (4119) [INFO] 
* 2023-08-26 01:34:36 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-26 01:34:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-26 01:34:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-26 01:34:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-26 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-26 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-26 01:34:37 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-26 01:34:37 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-26 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-26 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-26 01:34:37 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-26 01:34:37 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-26 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-26 01:34:41 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-26 01:34:41 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-26 01:34:41 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-26 01:34:41 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-26 01:34:41 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-26 01:34:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-26 01:34:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y54ymine1g/ea_profile.json
* 2023-08-26 01:34:46 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y54ymine1g/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-26 01:34:46 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-27 01:34:25 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-27 01:34:25 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-27 01:34:25 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-27 01:34:25 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-27 01:34:25 (4089) [INFO] 
* 2023-08-27 01:34:25 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-27 01:34:25 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-27 01:34:25 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-27 01:34:25 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-27 01:34:25 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-27 01:34:25 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-27 01:34:25 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-27 01:34:25 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-27 01:34:25 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-27 01:34:25 (4119) [INFO] 
* 2023-08-27 01:34:25 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-27 01:34:25 (4089) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-27 01:34:34 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-27 01:34:34 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-27 01:34:34 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-27 01:34:34 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-27 01:34:34 (4102) [INFO] Trying other mirror.
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-27 01:34:34 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-27 01:34:34 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-27 01:34:34 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-27 01:34:34 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-27 01:34:34 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-27 01:34:34 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-27 01:34:34 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-27 01:34:34 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-27 01:34:34 (4102) [INFO]         or
* 2023-08-27 01:34:34 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-27 01:34:34 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-27 01:34:34 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-27 01:34:34 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-27 01:34:34 (4102) [INFO]         compromise:
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-27 01:34:34 (4102) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-27 01:34:34 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-27 01:34:34 (4119) [INFO] 
* 2023-08-27 01:34:34 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-27 01:34:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-27 01:34:34 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-27 01:34:35 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-27 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-27 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-27 01:34:35 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-27 01:34:35 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-27 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-27 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-27 01:34:35 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-27 01:34:35 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-27 01:34:35 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-27 01:34:38 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-27 01:34:38 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-27 01:34:38 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-27 01:34:38 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-27 01:34:38 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-27 01:34:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-27 01:34:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k9AJf1kClz/ea_profile.json
* 2023-08-27 01:34:54 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k9AJf1kClz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-27 01:34:54 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-28 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-28 01:33:45 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-28 01:33:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-28 01:33:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-28 01:33:45 (4089) [INFO] 
* 2023-08-28 01:33:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-28 01:33:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-28 01:33:46 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-28 01:33:46 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-28 01:33:46 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-28 01:33:46 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-28 01:33:46 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-28 01:33:46 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-28 01:33:46 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-28 01:33:46 (4119) [INFO] 
* 2023-08-28 01:33:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-28 01:33:46 (4089) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-28 01:33:55 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-28 01:33:55 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-28 01:33:55 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-28 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-28 01:33:55 (4102) [INFO] Trying other mirror.
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-28 01:33:55 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-28 01:33:55 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-28 01:33:55 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-28 01:33:55 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-28 01:33:55 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-28 01:33:55 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-28 01:33:55 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-28 01:33:55 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-28 01:33:55 (4102) [INFO]         or
* 2023-08-28 01:33:55 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-28 01:33:55 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-28 01:33:55 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-28 01:33:55 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-28 01:33:55 (4102) [INFO]         compromise:
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-28 01:33:55 (4102) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-28 01:33:55 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-28 01:33:55 (4119) [INFO] 
* 2023-08-28 01:33:55 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-28 01:33:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-28 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-28 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-28 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-28 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-28 01:33:57 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-28 01:33:57 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-28 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-28 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-28 01:33:57 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-28 01:33:57 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-28 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-28 01:34:01 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-28 01:34:01 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-28 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-28 01:34:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-28 01:34:01 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-28 01:34:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-28 01:34:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HvcQ40Xv9R/ea_profile.json
* 2023-08-28 01:34:09 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HvcQ40Xv9R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-28 01:34:09 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-29 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-29 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-29 01:33:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-29 01:33:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-29 01:33:40 (4089) [INFO] 
* 2023-08-29 01:33:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-29 01:33:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-29 01:33:41 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-29 01:33:41 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-29 01:33:41 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-29 01:33:41 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-29 01:33:41 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-29 01:33:41 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-29 01:33:41 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-29 01:33:41 (4119) [INFO] 
* 2023-08-29 01:33:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-29 01:33:41 (4089) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-29 01:33:51 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-29 01:33:51 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-29 01:33:51 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-29 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-29 01:33:51 (4102) [INFO] Trying other mirror.
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-29 01:33:51 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-29 01:33:51 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-29 01:33:51 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-29 01:33:51 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-29 01:33:51 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-29 01:33:51 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-29 01:33:51 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-29 01:33:51 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-29 01:33:51 (4102) [INFO]         or
* 2023-08-29 01:33:51 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-29 01:33:51 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-29 01:33:51 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-29 01:33:51 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-29 01:33:51 (4102) [INFO]         compromise:
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-29 01:33:51 (4102) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-29 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-29 01:33:51 (4119) [INFO] 
* 2023-08-29 01:33:51 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-29 01:33:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-29 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-29 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-29 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-29 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-29 01:33:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-29 01:33:52 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-29 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-29 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-29 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-29 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-29 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-29 01:33:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-29 01:33:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-29 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-29 01:33:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-29 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-29 01:33:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-29 01:33:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZsZsMohYSS/ea_profile.json
* 2023-08-29 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZsZsMohYSS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-29 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-30 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-30 01:33:41 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-30 01:33:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-30 01:33:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-30 01:33:41 (4089) [INFO] 
* 2023-08-30 01:33:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-30 01:33:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-30 01:33:41 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-30 01:33:41 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-30 01:33:41 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-30 01:33:41 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-30 01:33:41 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-30 01:33:41 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-30 01:33:41 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-30 01:33:41 (4119) [INFO] 
* 2023-08-30 01:33:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-30 01:33:41 (4089) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-30 01:33:50 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-30 01:33:50 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-30 01:33:50 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-30 01:33:50 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-30 01:33:50 (4102) [INFO] Trying other mirror.
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-30 01:33:50 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-30 01:33:50 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-30 01:33:50 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-30 01:33:50 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-30 01:33:50 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-30 01:33:50 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-30 01:33:50 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-30 01:33:50 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-30 01:33:50 (4102) [INFO]         or
* 2023-08-30 01:33:50 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-30 01:33:50 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-30 01:33:50 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-30 01:33:50 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-30 01:33:50 (4102) [INFO]         compromise:
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-30 01:33:50 (4102) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-30 01:33:50 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-30 01:33:50 (4119) [INFO] 
* 2023-08-30 01:33:50 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-30 01:33:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-30 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-30 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-30 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-30 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-30 01:33:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-30 01:33:52 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-30 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-30 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-30 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-30 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-30 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-30 01:33:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-30 01:33:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-30 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-30 01:33:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-30 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-30 01:33:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-30 01:33:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/__BU1PASsv/ea_profile.json
* 2023-08-30 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/__BU1PASsv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-30 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-31 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-08-31 01:33:40 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-08-31 01:33:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-31 01:33:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-31 01:33:40 (4089) [INFO] 
* 2023-08-31 01:33:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-31 01:33:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-08-31 01:33:40 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-08-31 01:33:40 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-08-31 01:33:40 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-08-31 01:33:40 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-08-31 01:33:40 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-08-31 01:33:40 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-08-31 01:33:40 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-08-31 01:33:40 (4119) [INFO] 
* 2023-08-31 01:33:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-31 01:33:40 (4089) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-08-31 01:33:51 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-08-31 01:33:51 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-08-31 01:33:51 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-08-31 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-31 01:33:51 (4102) [INFO] Trying other mirror.
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-08-31 01:33:51 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-31 01:33:51 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-31 01:33:51 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-31 01:33:51 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-31 01:33:51 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-31 01:33:51 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-31 01:33:51 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-31 01:33:51 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-08-31 01:33:51 (4102) [INFO]         or
* 2023-08-31 01:33:51 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-31 01:33:51 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-31 01:33:51 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-31 01:33:51 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-31 01:33:51 (4102) [INFO]         compromise:
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-08-31 01:33:51 (4102) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-08-31 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-31 01:33:51 (4119) [INFO] 
* 2023-08-31 01:33:51 (4102) [INFO] Is this ok [y/N]: 
* 2023-08-31 01:33:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-31 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-31 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-08-31 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-08-31 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-08-31 01:33:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-08-31 01:33:53 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-08-31 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-08-31 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-08-31 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-08-31 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-08-31 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-31 01:33:56 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-31 01:33:56 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-08-31 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-31 01:33:56 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-08-31 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-08-31 01:33:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-31 01:33:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ABDQOwmWII/ea_profile.json
* 2023-08-31 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ABDQOwmWII/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-08-31 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-01 01:33:43 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-01 01:33:43 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-01 01:33:43 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-01 01:33:43 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-01 01:33:43 (4089) [INFO] 
* 2023-09-01 01:33:44 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-01 01:33:44 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-01 01:33:44 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-01 01:33:44 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-01 01:33:44 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-01 01:33:44 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-01 01:33:44 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-01 01:33:44 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-01 01:33:44 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-01 01:33:44 (4119) [INFO] 
* 2023-09-01 01:33:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-01 01:33:44 (4089) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-01 01:33:53 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-01 01:33:53 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-01 01:33:53 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-01 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-01 01:33:53 (4102) [INFO] Trying other mirror.
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-01 01:33:53 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-01 01:33:53 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-01 01:33:53 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-01 01:33:53 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-01 01:33:53 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-01 01:33:53 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-01 01:33:53 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-01 01:33:53 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-01 01:33:53 (4102) [INFO]         or
* 2023-09-01 01:33:53 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-01 01:33:53 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-01 01:33:53 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-01 01:33:53 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-01 01:33:53 (4102) [INFO]         compromise:
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-01 01:33:53 (4102) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-01 01:33:53 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-01 01:33:53 (4119) [INFO] 
* 2023-09-01 01:33:53 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-01 01:33:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-01 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-01 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-01 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-01 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-01 01:33:55 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-01 01:33:55 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-01 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-01 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-01 01:33:55 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-01 01:33:55 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-01 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-01 01:34:00 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-01 01:34:00 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-01 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-01 01:34:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-01 01:34:00 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-01 01:34:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-01 01:34:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wogTc3MNbE/ea_profile.json
* 2023-09-01 01:34:08 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wogTc3MNbE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-01 01:34:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-02 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-02 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-02 01:34:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-02 01:34:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-02 01:34:37 (4089) [INFO] 
* 2023-09-02 01:34:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-02 01:34:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-02 01:34:38 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-02 01:34:38 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-02 01:34:38 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-02 01:34:38 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-02 01:34:38 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-02 01:34:38 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-02 01:34:38 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-02 01:34:38 (4119) [INFO] 
* 2023-09-02 01:34:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-02 01:34:38 (4089) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-02 01:34:47 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-02 01:34:47 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-02 01:34:47 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-02 01:34:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-02 01:34:47 (4102) [INFO] Trying other mirror.
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-02 01:34:47 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-02 01:34:47 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-02 01:34:47 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-02 01:34:47 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-02 01:34:47 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-02 01:34:47 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-02 01:34:47 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-02 01:34:47 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-02 01:34:47 (4102) [INFO]         or
* 2023-09-02 01:34:47 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-02 01:34:47 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-02 01:34:47 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-02 01:34:47 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-02 01:34:47 (4102) [INFO]         compromise:
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-02 01:34:47 (4102) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-02 01:34:47 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-02 01:34:47 (4119) [INFO] 
* 2023-09-02 01:34:47 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-02 01:34:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-02 01:34:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-02 01:34:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-02 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-02 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-02 01:34:49 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-02 01:34:49 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-02 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-02 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-02 01:34:49 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-02 01:34:49 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-02 01:34:49 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-02 01:34:52 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-02 01:34:52 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-02 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-02 01:34:52 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-02 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-02 01:34:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-02 01:34:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fkxsiGj1j2/ea_profile.json
* 2023-09-02 01:34:58 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fkxsiGj1j2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-02 01:34:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-03 01:35:17 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-03 01:35:17 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-03 01:35:17 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-03 01:35:17 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-03 01:35:17 (4089) [INFO] 
* 2023-09-03 01:35:17 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-03 01:35:17 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-03 01:35:17 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-03 01:35:17 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-03 01:35:17 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-03 01:35:17 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-03 01:35:17 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-03 01:35:17 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-03 01:35:17 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-03 01:35:17 (4119) [INFO] 
* 2023-09-03 01:35:17 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-03 01:35:17 (4089) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-03 01:36:19 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-03 01:36:19 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-03 01:36:19 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-03 01:36:19 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-03 01:36:19 (4102) [INFO] Trying other mirror.
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-03 01:36:19 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-03 01:36:19 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-03 01:36:19 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-03 01:36:19 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-03 01:36:19 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-03 01:36:19 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-03 01:36:19 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-03 01:36:19 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-03 01:36:19 (4102) [INFO]         or
* 2023-09-03 01:36:19 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-03 01:36:19 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-03 01:36:19 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-03 01:36:19 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-03 01:36:19 (4102) [INFO]         compromise:
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-03 01:36:19 (4102) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-03 01:36:19 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-03 01:36:19 (4119) [INFO] 
* 2023-09-03 01:36:19 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-03 01:36:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-03 01:36:19 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-03 01:36:20 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-03 01:36:20 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-03 01:36:20 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-03 01:36:20 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-03 01:36:20 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-03 01:36:20 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-03 01:36:20 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-03 01:36:20 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-03 01:36:20 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-03 01:36:20 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-03 01:36:43 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-03 01:36:43 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-03 01:36:43 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-03 01:36:43 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-03 01:36:43 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-03 01:36:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-03 01:36:43 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sx0_XMiShX/ea_profile.json
* 2023-09-03 01:37:06 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sx0_XMiShX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-03 01:37:06 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-04 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-04 01:33:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-04 01:33:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-04 01:33:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-04 01:33:37 (4089) [INFO] 
* 2023-09-04 01:33:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-04 01:33:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-04 01:33:38 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-04 01:33:38 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-04 01:33:38 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-04 01:33:38 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-04 01:33:38 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-04 01:33:38 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-04 01:33:38 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-04 01:33:38 (4119) [INFO] 
* 2023-09-04 01:33:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-04 01:33:38 (4089) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-04 01:33:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-04 01:33:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-04 01:33:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-04 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-04 01:33:52 (4102) [INFO] Trying other mirror.
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-04 01:33:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-04 01:33:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-04 01:33:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-04 01:33:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-04 01:33:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-04 01:33:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-04 01:33:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-04 01:33:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-04 01:33:52 (4102) [INFO]         or
* 2023-09-04 01:33:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-04 01:33:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-04 01:33:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-04 01:33:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-04 01:33:52 (4102) [INFO]         compromise:
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-04 01:33:52 (4102) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-04 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-04 01:33:52 (4119) [INFO] 
* 2023-09-04 01:33:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-04 01:33:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-04 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-04 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-04 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-04 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-04 01:33:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-04 01:33:53 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-04 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-04 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-04 01:33:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-04 01:33:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-04 01:33:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-04 01:33:56 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-04 01:33:56 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-04 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-04 01:33:56 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-04 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-04 01:33:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-04 01:33:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KTR9AovxC7/ea_profile.json
* 2023-09-04 01:34:02 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KTR9AovxC7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-04 01:34:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-05 01:33:42 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-05 01:33:43 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-05 01:33:43 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-05 01:33:43 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-05 01:33:43 (4089) [INFO] 
* 2023-09-05 01:33:43 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-05 01:33:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-05 01:33:43 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-05 01:33:43 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-05 01:33:43 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-05 01:33:43 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-05 01:33:43 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-05 01:33:43 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-05 01:33:43 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-05 01:33:43 (4119) [INFO] 
* 2023-09-05 01:33:43 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-05 01:33:43 (4089) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-05 01:33:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-05 01:33:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-05 01:33:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-05 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-05 01:33:52 (4102) [INFO] Trying other mirror.
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-05 01:33:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-05 01:33:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-05 01:33:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-05 01:33:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-05 01:33:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-05 01:33:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-05 01:33:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-05 01:33:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-05 01:33:52 (4102) [INFO]         or
* 2023-09-05 01:33:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-05 01:33:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-05 01:33:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-05 01:33:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-05 01:33:52 (4102) [INFO]         compromise:
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-05 01:33:52 (4102) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-05 01:33:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-05 01:33:52 (4119) [INFO] 
* 2023-09-05 01:33:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-05 01:33:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-05 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-05 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-05 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-05 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-05 01:33:54 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-05 01:33:54 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-05 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-05 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-05 01:33:54 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-05 01:33:54 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-05 01:33:54 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-05 01:33:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-05 01:33:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-05 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-05 01:33:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-05 01:33:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-05 01:33:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-05 01:33:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nDLX42JGqO/ea_profile.json
* 2023-09-05 01:34:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nDLX42JGqO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-05 01:34:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-06 01:33:32 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-06 01:33:33 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-06 01:33:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-06 01:33:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-06 01:33:33 (4089) [INFO] 
* 2023-09-06 01:33:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-06 01:33:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-06 01:33:34 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-06 01:33:34 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-06 01:33:34 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-06 01:33:34 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-06 01:33:34 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-06 01:33:34 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-06 01:33:34 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-06 01:33:34 (4119) [INFO] 
* 2023-09-06 01:33:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-06 01:33:34 (4089) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-06 01:33:44 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-06 01:33:44 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-06 01:33:44 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-06 01:33:44 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-06 01:33:44 (4102) [INFO] Trying other mirror.
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-06 01:33:44 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-06 01:33:44 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-06 01:33:44 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-06 01:33:44 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-06 01:33:44 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-06 01:33:44 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-06 01:33:44 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-06 01:33:44 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-06 01:33:44 (4102) [INFO]         or
* 2023-09-06 01:33:44 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-06 01:33:44 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-06 01:33:44 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-06 01:33:44 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-06 01:33:44 (4102) [INFO]         compromise:
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-06 01:33:44 (4102) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-06 01:33:44 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-06 01:33:44 (4119) [INFO] 
* 2023-09-06 01:33:44 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-06 01:33:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-06 01:33:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-06 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-06 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-06 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-06 01:33:46 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-06 01:33:46 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-06 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-06 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-06 01:33:46 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-06 01:33:46 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-06 01:33:46 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-06 01:33:50 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-06 01:33:50 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-06 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-06 01:33:50 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-06 01:33:50 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-06 01:33:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-06 01:33:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/l313gUrDCa/ea_profile.json
* 2023-09-06 01:33:57 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/l313gUrDCa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-06 01:33:57 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-07 01:33:58 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-07 01:33:59 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-07 01:33:59 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-07 01:33:59 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-07 01:33:59 (4089) [INFO] 
* 2023-09-07 01:33:59 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-07 01:33:59 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-07 01:33:59 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-07 01:33:59 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-07 01:33:59 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-07 01:33:59 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-07 01:33:59 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-07 01:33:59 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-07 01:33:59 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-07 01:33:59 (4119) [INFO] 
* 2023-09-07 01:33:59 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-07 01:33:59 (4089) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-07 01:34:11 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-07 01:34:11 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-07 01:34:11 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-07 01:34:11 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-07 01:34:11 (4102) [INFO] Trying other mirror.
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-07 01:34:11 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-07 01:34:11 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-07 01:34:11 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-07 01:34:11 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-07 01:34:11 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-07 01:34:11 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-07 01:34:11 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-07 01:34:11 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-07 01:34:11 (4102) [INFO]         or
* 2023-09-07 01:34:11 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-07 01:34:11 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-07 01:34:11 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-07 01:34:11 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-07 01:34:11 (4102) [INFO]         compromise:
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-07 01:34:11 (4102) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-07 01:34:11 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-07 01:34:11 (4119) [INFO] 
* 2023-09-07 01:34:11 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-07 01:34:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-07 01:34:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-07 01:34:13 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-07 01:34:13 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-07 01:34:13 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-07 01:34:13 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-07 01:34:13 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-07 01:34:13 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-07 01:34:13 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-07 01:34:13 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-07 01:34:13 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-07 01:34:13 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-07 01:34:16 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-07 01:34:16 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-07 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-07 01:34:16 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-07 01:34:16 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-07 01:34:16 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-07 01:34:16 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WZSTe_BVdD/ea_profile.json
* 2023-09-07 01:34:21 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WZSTe_BVdD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-07 01:34:21 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-08 01:33:35 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-08 01:33:36 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-08 01:33:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-08 01:33:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-08 01:33:36 (4089) [INFO] 
* 2023-09-08 01:33:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-08 01:33:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-08 01:33:36 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-08 01:33:36 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-08 01:33:36 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-08 01:33:36 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-08 01:33:36 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-08 01:33:36 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-08 01:33:36 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-08 01:33:36 (4119) [INFO] 
* 2023-09-08 01:33:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-08 01:33:36 (4089) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-08 01:33:51 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-08 01:33:51 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-08 01:33:51 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-08 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-08 01:33:51 (4102) [INFO] Trying other mirror.
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-08 01:33:51 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-08 01:33:51 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-08 01:33:51 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-08 01:33:51 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-08 01:33:51 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-08 01:33:51 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-08 01:33:51 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-08 01:33:51 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-08 01:33:51 (4102) [INFO]         or
* 2023-09-08 01:33:51 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-08 01:33:51 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-08 01:33:51 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-08 01:33:51 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-08 01:33:51 (4102) [INFO]         compromise:
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-08 01:33:51 (4102) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-08 01:33:51 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-08 01:33:51 (4119) [INFO] 
* 2023-09-08 01:33:51 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-08 01:33:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-08 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-08 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-08 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-08 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-08 01:33:52 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-08 01:33:52 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-08 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-08 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-08 01:33:52 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-08 01:33:52 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-08 01:33:52 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-08 01:33:56 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-08 01:33:56 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-08 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-08 01:33:56 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-08 01:33:56 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-08 01:33:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-08 01:33:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RxdFdYjXIX/ea_profile.json
* 2023-09-08 01:34:01 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RxdFdYjXIX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-08 01:34:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-09 01:34:36 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-09 01:34:37 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-09 01:34:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-09 01:34:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-09 01:34:37 (4089) [INFO] 
* 2023-09-09 01:34:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-09 01:34:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-09 01:34:37 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-09 01:34:37 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-09 01:34:37 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-09 01:34:37 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-09 01:34:37 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-09 01:34:37 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-09 01:34:37 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-09 01:34:37 (4119) [INFO] 
* 2023-09-09 01:34:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-09 01:34:37 (4089) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-09 01:34:52 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-09 01:34:52 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-09 01:34:52 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-09 01:34:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-09 01:34:52 (4102) [INFO] Trying other mirror.
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-09 01:34:52 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-09 01:34:52 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-09 01:34:52 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-09 01:34:52 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-09 01:34:52 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-09 01:34:52 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-09 01:34:52 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-09 01:34:52 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-09 01:34:52 (4102) [INFO]         or
* 2023-09-09 01:34:52 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-09 01:34:52 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-09 01:34:52 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-09 01:34:52 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-09 01:34:52 (4102) [INFO]         compromise:
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-09 01:34:52 (4102) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-09 01:34:52 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-09 01:34:52 (4119) [INFO] 
* 2023-09-09 01:34:52 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-09 01:34:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-09 01:34:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-09 01:34:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-09 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-09 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-09 01:34:53 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-09 01:34:53 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-09 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-09 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-09 01:34:53 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-09 01:34:53 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-09 01:34:53 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-09 01:34:57 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-09 01:34:57 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-09 01:34:57 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-09 01:34:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-09 01:34:57 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-09 01:34:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-09 01:34:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/obWGZPXmFJ/ea_profile.json
* 2023-09-09 01:35:03 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/obWGZPXmFJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-09 01:35:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-10 01:34:43 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-10 01:34:43 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-10 01:34:43 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-10 01:34:43 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-10 01:34:43 (4089) [INFO] 
* 2023-09-10 01:34:43 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-10 01:34:44 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-10 01:34:44 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-10 01:34:44 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-10 01:34:44 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-10 01:34:44 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-10 01:34:44 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-10 01:34:44 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-10 01:34:44 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-10 01:34:44 (4119) [INFO] 
* 2023-09-10 01:34:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-10 01:34:44 (4089) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-10 01:34:59 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-10 01:34:59 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-10 01:34:59 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-10 01:34:59 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-10 01:34:59 (4102) [INFO] Trying other mirror.
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-10 01:34:59 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-10 01:34:59 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-10 01:34:59 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-10 01:34:59 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-10 01:34:59 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-10 01:34:59 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-10 01:34:59 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-10 01:34:59 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-10 01:34:59 (4102) [INFO]         or
* 2023-09-10 01:34:59 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-10 01:34:59 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-10 01:34:59 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-10 01:34:59 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-10 01:34:59 (4102) [INFO]         compromise:
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-10 01:34:59 (4102) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-10 01:34:59 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-10 01:34:59 (4119) [INFO] 
* 2023-09-10 01:34:59 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-10 01:34:59 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-10 01:34:59 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-10 01:35:01 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-10 01:35:01 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-10 01:35:01 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-10 01:35:01 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-10 01:35:01 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-10 01:35:01 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-10 01:35:01 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-10 01:35:01 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-10 01:35:01 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-10 01:35:01 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-10 01:35:04 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-10 01:35:04 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-10 01:35:04 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-10 01:35:04 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-10 01:35:04 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-10 01:35:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-10 01:35:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gzxii6f7w6/ea_profile.json
* 2023-09-10 01:35:09 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gzxii6f7w6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-10 01:35:09 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-11 01:33:38 (153) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment, which this script cannot support at this time.
* 2023-09-11 01:33:39 (153) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-11 01:33:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-11 01:33:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-11 01:33:39 (4089) [INFO] 
* 2023-09-11 01:33:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-11 01:33:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-11 01:33:39 (4102) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-11 01:33:39 (4102) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-11 01:33:39 (4102) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-11 01:33:39 (4102) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-11 01:33:39 (4102) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-11 01:33:39 (4102) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-11 01:33:39 (4102) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-11 01:33:39 (4119) [INFO] 
* 2023-09-11 01:33:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-11 01:33:39 (4089) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-11 01:33:49 (4102) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-11 01:33:49 (4102) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-11 01:33:49 (4102) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-11 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-11 01:33:49 (4102) [INFO] Trying other mirror.
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-11 01:33:49 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-11 01:33:49 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-11 01:33:49 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-11 01:33:49 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-11 01:33:49 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-11 01:33:49 (4102) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-11 01:33:49 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-11 01:33:49 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-11 01:33:49 (4102) [INFO]         or
* 2023-09-11 01:33:49 (4102) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-11 01:33:49 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-11 01:33:49 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-11 01:33:49 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-11 01:33:49 (4102) [INFO]         compromise:
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-11 01:33:49 (4102) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-11 01:33:49 (4102) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-11 01:33:49 (4119) [INFO] 
* 2023-09-11 01:33:49 (4102) [INFO] Is this ok [y/N]: 
* 2023-09-11 01:33:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-11 01:33:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-11 01:33:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-11 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-11 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-11 01:33:51 (1625) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-11 01:33:51 (1625) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-11 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-11 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-11 01:33:51 (1625) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-11 01:33:51 (1636) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-11 01:33:51 (153) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-11 01:33:55 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-11 01:33:55 (1567) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-11 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-11 01:33:55 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-11 01:33:55 (153) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-11 01:33:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-11 01:33:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cbjoeRUR3Q/ea_profile.json
* 2023-09-11 01:34:00 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cbjoeRUR3Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-09-11 01:34:00 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-12 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-12 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-12 01:33:43 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-12 01:33:43 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-12 01:33:43 (4229) [INFO] 
* 2023-09-12 01:33:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-12 01:33:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-12 01:33:43 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-12 01:33:43 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-12 01:33:43 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-12 01:33:43 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-12 01:33:43 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-12 01:33:43 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-12 01:33:43 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-12 01:33:43 (4259) [INFO] 
* 2023-09-12 01:33:43 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-12 01:33:43 (4229) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-12 01:33:53 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-12 01:33:53 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-12 01:33:53 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-12 01:33:53 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-12 01:33:53 (4242) [INFO] Trying other mirror.
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-12 01:33:53 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-12 01:33:53 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-12 01:33:53 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-12 01:33:53 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-12 01:33:53 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-12 01:33:53 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-12 01:33:53 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-12 01:33:53 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-12 01:33:53 (4242) [INFO]         or
* 2023-09-12 01:33:53 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-12 01:33:53 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-12 01:33:53 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-12 01:33:53 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-12 01:33:53 (4242) [INFO]         compromise:
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-12 01:33:53 (4242) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-12 01:33:53 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-12 01:33:53 (4259) [INFO] 
* 2023-09-12 01:33:53 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-12 01:33:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-12 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-12 01:33:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-12 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-12 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-12 01:33:54 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-12 01:33:54 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-12 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-12 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-12 01:33:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-12 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-12 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-12 01:33:58 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-12 01:33:58 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-12 01:33:58 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-12 01:33:58 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-12 01:33:58 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-12 01:33:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-12 01:33:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/T5OcHK5Fui/ea_profile.json
* 2023-09-12 01:34:04 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/T5OcHK5Fui/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-12 01:34:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-13 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-13 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-13 01:33:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-13 01:33:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-13 01:33:40 (4229) [INFO] 
* 2023-09-13 01:33:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-13 01:33:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-13 01:33:41 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-13 01:33:41 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-13 01:33:41 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-13 01:33:41 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-13 01:33:41 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-13 01:33:41 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-13 01:33:41 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-13 01:33:41 (4259) [INFO] 
* 2023-09-13 01:33:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-13 01:33:41 (4229) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-13 01:34:04 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-13 01:34:04 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-13 01:34:04 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-13 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-13 01:34:04 (4242) [INFO] Trying other mirror.
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-13 01:34:04 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-13 01:34:04 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-13 01:34:04 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-13 01:34:04 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-13 01:34:04 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-13 01:34:04 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-13 01:34:04 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-13 01:34:04 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-13 01:34:04 (4242) [INFO]         or
* 2023-09-13 01:34:04 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-13 01:34:04 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-13 01:34:04 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-13 01:34:04 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-13 01:34:04 (4242) [INFO]         compromise:
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-13 01:34:04 (4242) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-13 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-13 01:34:04 (4259) [INFO] 
* 2023-09-13 01:34:04 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-13 01:34:04 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-13 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-13 01:34:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-13 01:34:06 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-13 01:34:06 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-13 01:34:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-13 01:34:06 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-13 01:34:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-13 01:34:10 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-13 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-13 01:34:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-13 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-13 01:34:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-13 01:34:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JrRx9Ph75g/ea_profile.json
* 2023-09-13 01:34:45 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JrRx9Ph75g/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-13 01:34:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-14 01:33:37 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-14 01:33:37 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-14 01:33:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-14 01:33:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-14 01:33:37 (4229) [INFO] 
* 2023-09-14 01:33:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-14 01:33:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-14 01:33:38 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-14 01:33:38 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-14 01:33:38 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-14 01:33:38 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-14 01:33:38 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-14 01:33:38 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-14 01:33:38 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-14 01:33:38 (4259) [INFO] 
* 2023-09-14 01:33:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-14 01:33:38 (4229) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-14 01:33:47 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-14 01:33:47 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-14 01:33:47 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-14 01:33:47 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-14 01:33:47 (4242) [INFO] Trying other mirror.
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-14 01:33:47 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-14 01:33:47 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-14 01:33:47 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-14 01:33:47 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-14 01:33:47 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-14 01:33:47 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-14 01:33:47 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-14 01:33:47 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-14 01:33:47 (4242) [INFO]         or
* 2023-09-14 01:33:47 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-14 01:33:47 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-14 01:33:47 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-14 01:33:47 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-14 01:33:47 (4242) [INFO]         compromise:
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-14 01:33:47 (4242) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-14 01:33:47 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-14 01:33:47 (4259) [INFO] 
* 2023-09-14 01:33:47 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-14 01:33:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-14 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-14 01:33:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-14 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-14 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-14 01:33:48 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-14 01:33:48 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-14 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-14 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-14 01:33:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-14 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-14 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-14 01:33:51 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-14 01:33:51 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-14 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-14 01:33:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-14 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-14 01:33:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-14 01:33:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lnhR1Fyegg/ea_profile.json
* 2023-09-14 01:33:56 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lnhR1Fyegg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-14 01:33:56 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-15 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-15 01:33:37 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-15 01:33:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-15 01:33:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-15 01:33:37 (4229) [INFO] 
* 2023-09-15 01:33:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-15 01:33:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-15 01:33:37 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-15 01:33:37 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-15 01:33:37 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-15 01:33:37 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-15 01:33:37 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-15 01:33:37 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-15 01:33:37 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-15 01:33:37 (4259) [INFO] 
* 2023-09-15 01:33:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-15 01:33:37 (4229) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-15 01:33:47 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-15 01:33:47 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-15 01:33:47 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-15 01:33:47 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-15 01:33:47 (4242) [INFO] Trying other mirror.
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-15 01:33:47 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-15 01:33:47 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-15 01:33:47 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-15 01:33:47 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-15 01:33:47 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-15 01:33:47 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-15 01:33:47 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-15 01:33:47 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-15 01:33:47 (4242) [INFO]         or
* 2023-09-15 01:33:47 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-15 01:33:47 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-15 01:33:47 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-15 01:33:47 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-15 01:33:47 (4242) [INFO]         compromise:
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-15 01:33:47 (4242) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-15 01:33:47 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-15 01:33:47 (4259) [INFO] 
* 2023-09-15 01:33:47 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-15 01:33:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-15 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-15 01:33:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-15 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-15 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-15 01:33:48 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-15 01:33:48 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-15 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-15 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-15 01:33:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-15 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-15 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-15 01:33:51 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-15 01:33:51 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-15 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-15 01:33:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-15 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-15 01:33:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-15 01:33:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gOkpuuRu1E/ea_profile.json
* 2023-09-15 01:33:56 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gOkpuuRu1E/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-15 01:33:56 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-16 01:34:15 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-16 01:34:15 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-16 01:34:15 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-16 01:34:15 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-16 01:34:15 (4229) [INFO] 
* 2023-09-16 01:34:16 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-16 01:34:16 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-16 01:34:16 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-16 01:34:16 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-16 01:34:16 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-16 01:34:16 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-16 01:34:16 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-16 01:34:16 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-16 01:34:16 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-16 01:34:16 (4259) [INFO] 
* 2023-09-16 01:34:16 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-16 01:34:16 (4229) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-16 01:34:25 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-16 01:34:25 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-16 01:34:25 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-16 01:34:25 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-16 01:34:25 (4242) [INFO] Trying other mirror.
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-16 01:34:25 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-16 01:34:25 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-16 01:34:25 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-16 01:34:25 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-16 01:34:25 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-16 01:34:25 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-16 01:34:25 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-16 01:34:25 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-16 01:34:25 (4242) [INFO]         or
* 2023-09-16 01:34:25 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-16 01:34:25 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-16 01:34:25 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-16 01:34:25 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-16 01:34:25 (4242) [INFO]         compromise:
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-16 01:34:25 (4242) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-16 01:34:25 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-16 01:34:25 (4259) [INFO] 
* 2023-09-16 01:34:25 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-16 01:34:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-16 01:34:25 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-16 01:34:26 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-16 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-16 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-16 01:34:26 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-16 01:34:26 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-16 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-16 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-16 01:34:26 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-16 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-16 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-16 01:34:29 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-16 01:34:29 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-16 01:34:29 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-16 01:34:29 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-16 01:34:29 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-16 01:34:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-16 01:34:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iHNBbQZ4KT/ea_profile.json
* 2023-09-16 01:34:33 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iHNBbQZ4KT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-16 01:34:33 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-17 01:34:24 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-17 01:34:25 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-17 01:34:25 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-17 01:34:25 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-17 01:34:25 (4229) [INFO] 
* 2023-09-17 01:34:25 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-17 01:34:25 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-17 01:34:25 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-17 01:34:25 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-17 01:34:25 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-17 01:34:25 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-17 01:34:25 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-17 01:34:25 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-17 01:34:25 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-17 01:34:25 (4259) [INFO] 
* 2023-09-17 01:34:25 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-17 01:34:25 (4229) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-17 01:34:36 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-17 01:34:36 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-17 01:34:36 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-17 01:34:36 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-17 01:34:36 (4242) [INFO] Trying other mirror.
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-17 01:34:36 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-17 01:34:36 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-17 01:34:36 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-17 01:34:36 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-17 01:34:36 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-17 01:34:36 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-17 01:34:36 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-17 01:34:36 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-17 01:34:36 (4242) [INFO]         or
* 2023-09-17 01:34:36 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-17 01:34:36 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-17 01:34:36 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-17 01:34:36 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-17 01:34:36 (4242) [INFO]         compromise:
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-17 01:34:36 (4242) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-17 01:34:36 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-17 01:34:36 (4259) [INFO] 
* 2023-09-17 01:34:36 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-17 01:34:36 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-17 01:34:36 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-17 01:34:37 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-17 01:34:37 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-17 01:34:37 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-17 01:34:37 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-17 01:34:37 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-17 01:34:37 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-17 01:34:37 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-17 01:34:37 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-17 01:34:37 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-17 01:34:37 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-17 01:34:40 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-17 01:34:40 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-17 01:34:40 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-17 01:34:40 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-17 01:34:40 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-17 01:34:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-17 01:34:41 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6a8GVJF2Bx/ea_profile.json
* 2023-09-17 01:34:46 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6a8GVJF2Bx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-17 01:34:46 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-18 01:33:41 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-18 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-18 01:33:42 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-18 01:33:42 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-18 01:33:42 (4229) [INFO] 
* 2023-09-18 01:33:42 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-18 01:33:42 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-18 01:33:42 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-18 01:33:42 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-18 01:33:42 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-18 01:33:42 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-18 01:33:42 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-18 01:33:42 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-18 01:33:42 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-18 01:33:42 (4259) [INFO] 
* 2023-09-18 01:33:42 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-18 01:33:42 (4229) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-18 01:33:52 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-18 01:33:52 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-18 01:33:52 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-18 01:33:52 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-18 01:33:52 (4242) [INFO] Trying other mirror.
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-18 01:33:52 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-18 01:33:52 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-18 01:33:52 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-18 01:33:52 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-18 01:33:52 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-18 01:33:52 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-18 01:33:52 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-18 01:33:52 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-18 01:33:52 (4242) [INFO]         or
* 2023-09-18 01:33:52 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-18 01:33:52 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-18 01:33:52 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-18 01:33:52 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-18 01:33:52 (4242) [INFO]         compromise:
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-18 01:33:52 (4242) [INFO] 
* 2023-09-18 01:33:52 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-18 01:33:52 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-18 01:33:53 (4259) [INFO] 
* 2023-09-18 01:33:53 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-18 01:33:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-18 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-18 01:33:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-18 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-18 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-18 01:33:54 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-18 01:33:54 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-18 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-18 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-18 01:33:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-18 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-18 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-18 01:33:57 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-18 01:33:57 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-18 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-18 01:33:57 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-18 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-18 01:33:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-18 01:33:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c8bRyeWwJC/ea_profile.json
* 2023-09-18 01:34:02 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c8bRyeWwJC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-18 01:34:02 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-19 01:33:34 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-19 01:33:35 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-19 01:33:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-19 01:33:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-19 01:33:35 (4229) [INFO] 
* 2023-09-19 01:33:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-19 01:33:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-19 01:33:35 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-19 01:33:35 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-19 01:33:35 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-19 01:33:35 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-19 01:33:35 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-19 01:33:35 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-19 01:33:35 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-19 01:33:35 (4259) [INFO] 
* 2023-09-19 01:33:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-19 01:33:35 (4229) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-19 01:33:44 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-19 01:33:44 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-19 01:33:44 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-19 01:33:44 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-19 01:33:44 (4242) [INFO] Trying other mirror.
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-19 01:33:44 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-19 01:33:44 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-19 01:33:44 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-19 01:33:44 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-19 01:33:44 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-19 01:33:44 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-19 01:33:44 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-19 01:33:44 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-19 01:33:44 (4242) [INFO]         or
* 2023-09-19 01:33:44 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-19 01:33:44 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-19 01:33:44 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-19 01:33:44 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-19 01:33:44 (4242) [INFO]         compromise:
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-19 01:33:44 (4242) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-19 01:33:44 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-19 01:33:44 (4259) [INFO] 
* 2023-09-19 01:33:44 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-19 01:33:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-19 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-19 01:33:46 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-19 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-19 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-19 01:33:46 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-19 01:33:46 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-19 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-19 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-19 01:33:46 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-19 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-19 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-19 01:33:48 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-19 01:33:48 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-19 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-19 01:33:48 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-19 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-19 01:33:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-19 01:33:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3m4ZeluyiT/ea_profile.json
* 2023-09-19 01:33:53 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3m4ZeluyiT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-19 01:33:53 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-20 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-20 01:33:37 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-20 01:33:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-20 01:33:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-20 01:33:37 (4229) [INFO] 
* 2023-09-20 01:33:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-20 01:33:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-20 01:33:37 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-20 01:33:37 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-20 01:33:37 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-20 01:33:37 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-20 01:33:37 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-20 01:33:37 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-20 01:33:37 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-20 01:33:37 (4259) [INFO] 
* 2023-09-20 01:33:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-20 01:33:37 (4229) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-20 01:33:51 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-20 01:33:51 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-20 01:33:51 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-20 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-20 01:33:51 (4242) [INFO] Trying other mirror.
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-20 01:33:51 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-20 01:33:51 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-20 01:33:51 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-20 01:33:51 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-20 01:33:51 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-20 01:33:51 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-20 01:33:51 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-20 01:33:51 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-20 01:33:51 (4242) [INFO]         or
* 2023-09-20 01:33:51 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-20 01:33:51 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-20 01:33:51 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-20 01:33:51 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-20 01:33:51 (4242) [INFO]         compromise:
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-20 01:33:51 (4242) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-20 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-20 01:33:51 (4259) [INFO] 
* 2023-09-20 01:33:51 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-20 01:33:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-20 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-20 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-20 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-20 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-20 01:33:52 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-20 01:33:52 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-20 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-20 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-20 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-20 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-20 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-20 01:33:56 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-20 01:33:56 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-20 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-20 01:33:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-20 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-20 01:33:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-20 01:33:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wgmonwdROA/ea_profile.json
* 2023-09-20 01:34:00 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wgmonwdROA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-20 01:34:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-21 01:33:32 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-21 01:33:32 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-21 01:33:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-21 01:33:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-21 01:33:32 (4229) [INFO] 
* 2023-09-21 01:33:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-21 01:33:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-21 01:33:33 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-21 01:33:33 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-21 01:33:33 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-21 01:33:33 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-21 01:33:33 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-21 01:33:33 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-21 01:33:33 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-21 01:33:33 (4259) [INFO] 
* 2023-09-21 01:33:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-21 01:33:33 (4229) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-21 01:33:46 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-21 01:33:46 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-21 01:33:46 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-21 01:33:46 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-21 01:33:46 (4242) [INFO] Trying other mirror.
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-21 01:33:46 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-21 01:33:46 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-21 01:33:46 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-21 01:33:46 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-21 01:33:46 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-21 01:33:46 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-21 01:33:46 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-21 01:33:46 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-21 01:33:46 (4242) [INFO]         or
* 2023-09-21 01:33:46 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-21 01:33:46 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-21 01:33:46 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-21 01:33:46 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-21 01:33:46 (4242) [INFO]         compromise:
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-21 01:33:46 (4242) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-21 01:33:46 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-21 01:33:46 (4259) [INFO] 
* 2023-09-21 01:33:46 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-21 01:33:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-21 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-21 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-21 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-21 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-21 01:33:47 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-21 01:33:47 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-21 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-21 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-21 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-21 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-21 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-21 01:33:52 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-21 01:33:52 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-21 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-21 01:33:52 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-21 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-21 01:33:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-21 01:33:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Sb_9sFu4yH/ea_profile.json
* 2023-09-21 01:33:56 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Sb_9sFu4yH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-21 01:33:56 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-22 01:33:32 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-22 01:33:32 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-22 01:33:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-22 01:33:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-22 01:33:32 (4229) [INFO] 
* 2023-09-22 01:33:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-22 01:33:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-22 01:33:33 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-22 01:33:33 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-22 01:33:33 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-22 01:33:33 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-22 01:33:33 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-22 01:33:33 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-22 01:33:33 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-22 01:33:33 (4259) [INFO] 
* 2023-09-22 01:33:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-22 01:33:33 (4229) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-22 01:33:44 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-22 01:33:44 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-22 01:33:44 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-22 01:33:44 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-22 01:33:44 (4242) [INFO] Trying other mirror.
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-22 01:33:44 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-22 01:33:44 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-22 01:33:44 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-22 01:33:44 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-22 01:33:44 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-22 01:33:44 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-22 01:33:44 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-22 01:33:44 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-22 01:33:44 (4242) [INFO]         or
* 2023-09-22 01:33:44 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-22 01:33:44 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-22 01:33:44 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-22 01:33:44 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-22 01:33:44 (4242) [INFO]         compromise:
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-22 01:33:44 (4242) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-22 01:33:44 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-22 01:33:44 (4259) [INFO] 
* 2023-09-22 01:33:44 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-22 01:33:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-22 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-22 01:33:45 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-22 01:33:45 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-22 01:33:45 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-22 01:33:45 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-22 01:33:45 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-22 01:33:45 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-22 01:33:45 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-22 01:33:45 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-22 01:33:45 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-22 01:33:45 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-22 01:33:48 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-22 01:33:48 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-22 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-22 01:33:48 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-22 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-22 01:33:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-22 01:33:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mTBp2fQtZF/ea_profile.json
* 2023-09-22 01:33:51 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mTBp2fQtZF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-22 01:33:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-23 01:34:19 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-23 01:34:19 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-23 01:34:19 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-23 01:34:19 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-23 01:34:19 (4229) [INFO] 
* 2023-09-23 01:34:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-23 01:34:20 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-23 01:34:20 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-23 01:34:20 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-23 01:34:20 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-23 01:34:20 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-23 01:34:20 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-23 01:34:20 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-23 01:34:20 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-23 01:34:20 (4259) [INFO] 
* 2023-09-23 01:34:20 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-23 01:34:20 (4229) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-23 01:34:32 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-23 01:34:32 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-23 01:34:32 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-23 01:34:32 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-23 01:34:32 (4242) [INFO] Trying other mirror.
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-23 01:34:32 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-23 01:34:32 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-23 01:34:32 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-23 01:34:32 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-23 01:34:32 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-23 01:34:32 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-23 01:34:32 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-23 01:34:32 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-23 01:34:32 (4242) [INFO]         or
* 2023-09-23 01:34:32 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-23 01:34:32 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-23 01:34:32 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-23 01:34:32 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-23 01:34:32 (4242) [INFO]         compromise:
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-23 01:34:32 (4242) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-23 01:34:32 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-23 01:34:32 (4259) [INFO] 
* 2023-09-23 01:34:32 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-23 01:34:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-23 01:34:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-23 01:34:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-23 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-23 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-23 01:34:33 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-23 01:34:33 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-23 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-23 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-23 01:34:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-23 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-23 01:34:33 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-23 01:34:39 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-23 01:34:39 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-23 01:34:39 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-23 01:34:39 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-23 01:34:39 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-23 01:34:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-23 01:34:39 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ellOph3c4Q/ea_profile.json
* 2023-09-23 01:34:45 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ellOph3c4Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-23 01:34:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-24 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-24 01:34:08 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-24 01:34:08 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-24 01:34:08 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-24 01:34:08 (4229) [INFO] 
* 2023-09-24 01:34:08 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-24 01:34:08 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-24 01:34:08 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-24 01:34:08 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-24 01:34:08 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-24 01:34:08 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-24 01:34:08 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-24 01:34:08 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-24 01:34:09 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-24 01:34:09 (4259) [INFO] 
* 2023-09-24 01:34:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-24 01:34:09 (4229) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-24 01:34:20 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-24 01:34:20 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-24 01:34:20 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-24 01:34:20 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-24 01:34:20 (4242) [INFO] Trying other mirror.
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-24 01:34:20 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-24 01:34:20 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-24 01:34:20 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-24 01:34:20 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-24 01:34:20 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-24 01:34:20 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-24 01:34:20 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-24 01:34:20 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-24 01:34:20 (4242) [INFO]         or
* 2023-09-24 01:34:20 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-24 01:34:20 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-24 01:34:20 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-24 01:34:20 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-24 01:34:20 (4242) [INFO]         compromise:
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-24 01:34:20 (4242) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-24 01:34:20 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-24 01:34:20 (4259) [INFO] 
* 2023-09-24 01:34:20 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-24 01:34:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-24 01:34:20 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-24 01:34:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-24 01:34:22 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-24 01:34:22 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-24 01:34:22 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-24 01:34:22 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-24 01:34:22 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-24 01:34:22 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-24 01:34:22 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-24 01:34:22 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-24 01:34:22 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-24 01:34:26 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-24 01:34:26 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-24 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-24 01:34:26 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-24 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-24 01:34:26 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-24 01:34:26 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ju7or2g2uz/ea_profile.json
* 2023-09-24 01:34:30 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ju7or2g2uz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-24 01:34:30 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-25 01:33:27 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-25 01:33:28 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-25 01:33:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-25 01:33:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-25 01:33:28 (4229) [INFO] 
* 2023-09-25 01:33:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-25 01:33:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-25 01:33:28 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-25 01:33:28 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-25 01:33:28 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-25 01:33:28 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-25 01:33:28 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-25 01:33:28 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-25 01:33:28 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-25 01:33:28 (4259) [INFO] 
* 2023-09-25 01:33:28 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-25 01:33:28 (4229) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-25 01:33:38 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-25 01:33:38 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-25 01:33:38 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-25 01:33:38 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-25 01:33:38 (4242) [INFO] Trying other mirror.
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-25 01:33:38 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-25 01:33:38 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-25 01:33:38 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-25 01:33:38 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-25 01:33:38 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-25 01:33:38 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-25 01:33:38 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-25 01:33:38 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-25 01:33:38 (4242) [INFO]         or
* 2023-09-25 01:33:38 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-25 01:33:38 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-25 01:33:38 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-25 01:33:38 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-25 01:33:38 (4242) [INFO]         compromise:
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-25 01:33:38 (4242) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-25 01:33:38 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-25 01:33:38 (4259) [INFO] 
* 2023-09-25 01:33:38 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-25 01:33:38 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-25 01:33:38 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-25 01:33:39 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-25 01:33:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-25 01:33:39 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-25 01:33:39 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-25 01:33:39 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-25 01:33:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-25 01:33:39 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-25 01:33:39 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-25 01:33:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-25 01:33:39 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-25 01:33:42 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-25 01:33:42 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-25 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-25 01:33:42 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-25 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-25 01:33:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-25 01:33:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zRYR04P9Cr/ea_profile.json
* 2023-09-25 01:33:46 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zRYR04P9Cr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-25 01:33:46 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-26 01:33:32 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-26 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-26 01:33:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-26 01:33:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-26 01:33:33 (4229) [INFO] 
* 2023-09-26 01:33:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-26 01:33:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-26 01:33:33 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-26 01:33:33 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-26 01:33:33 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-26 01:33:33 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-26 01:33:33 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-26 01:33:33 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-26 01:33:33 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-26 01:33:33 (4259) [INFO] 
* 2023-09-26 01:33:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-26 01:33:33 (4229) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-26 01:33:42 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-26 01:33:42 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-26 01:33:42 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-26 01:33:42 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-26 01:33:42 (4242) [INFO] Trying other mirror.
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-26 01:33:42 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-26 01:33:42 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-26 01:33:42 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-26 01:33:42 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-26 01:33:42 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-26 01:33:42 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-26 01:33:42 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-26 01:33:42 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-26 01:33:42 (4242) [INFO]         or
* 2023-09-26 01:33:42 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-26 01:33:42 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-26 01:33:42 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-26 01:33:42 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-26 01:33:42 (4242) [INFO]         compromise:
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-26 01:33:42 (4242) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-26 01:33:42 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-26 01:33:42 (4259) [INFO] 
* 2023-09-26 01:33:42 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-26 01:33:42 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-26 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-26 01:33:44 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-26 01:33:44 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-26 01:33:44 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-26 01:33:44 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-26 01:33:44 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-26 01:33:44 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-26 01:33:44 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-26 01:33:44 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-26 01:33:44 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-26 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-26 01:33:46 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-26 01:33:46 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-26 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-26 01:33:46 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-26 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-26 01:33:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-26 01:33:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1LFkiGRk9k/ea_profile.json
* 2023-09-26 01:33:53 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1LFkiGRk9k/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-26 01:33:53 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-27 01:33:28 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-27 01:33:28 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-27 01:33:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-27 01:33:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-27 01:33:28 (4229) [INFO] 
* 2023-09-27 01:33:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-27 01:33:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-27 01:33:29 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-27 01:33:29 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-27 01:33:29 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-27 01:33:29 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-27 01:33:29 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-27 01:33:29 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-27 01:33:29 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-27 01:33:29 (4259) [INFO] 
* 2023-09-27 01:33:29 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-27 01:33:29 (4229) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-27 01:33:36 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-27 01:33:36 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-27 01:33:36 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-27 01:33:36 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-27 01:33:36 (4242) [INFO] Trying other mirror.
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-27 01:33:36 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-27 01:33:36 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-27 01:33:36 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-27 01:33:36 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-27 01:33:36 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-27 01:33:36 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-27 01:33:36 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-27 01:33:36 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-27 01:33:36 (4242) [INFO]         or
* 2023-09-27 01:33:36 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-27 01:33:36 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-27 01:33:36 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-27 01:33:36 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-27 01:33:36 (4242) [INFO]         compromise:
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-27 01:33:36 (4242) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-27 01:33:36 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-27 01:33:36 (4259) [INFO] 
* 2023-09-27 01:33:36 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-27 01:33:36 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-27 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-27 01:33:38 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-27 01:33:38 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-27 01:33:38 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-27 01:33:38 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-27 01:33:38 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-27 01:33:38 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-27 01:33:38 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-27 01:33:38 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-27 01:33:38 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-27 01:33:38 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-27 01:33:41 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-27 01:33:41 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-27 01:33:41 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-27 01:33:41 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-27 01:33:41 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-27 01:33:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-27 01:33:41 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TyFVt0S4hh/ea_profile.json
* 2023-09-27 01:33:45 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TyFVt0S4hh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-27 01:33:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-28 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-28 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-28 01:33:44 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-28 01:33:44 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-28 01:33:44 (4229) [INFO] 
* 2023-09-28 01:33:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-28 01:33:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-28 01:33:45 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-28 01:33:45 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-28 01:33:45 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-28 01:33:45 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-28 01:33:45 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-28 01:33:45 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-28 01:33:45 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-28 01:33:45 (4259) [INFO] 
* 2023-09-28 01:33:45 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-28 01:33:45 (4229) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-28 01:33:57 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-28 01:33:57 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-28 01:33:57 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-28 01:33:57 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-28 01:33:57 (4242) [INFO] Trying other mirror.
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-28 01:33:57 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-28 01:33:57 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-28 01:33:57 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-28 01:33:57 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-28 01:33:57 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-28 01:33:57 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-28 01:33:57 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-28 01:33:57 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-28 01:33:57 (4242) [INFO]         or
* 2023-09-28 01:33:57 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-28 01:33:57 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-28 01:33:57 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-28 01:33:57 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-28 01:33:57 (4242) [INFO]         compromise:
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-28 01:33:57 (4242) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-28 01:33:57 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-28 01:33:57 (4259) [INFO] 
* 2023-09-28 01:33:57 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-28 01:33:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-28 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-28 01:33:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-28 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-28 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-28 01:33:59 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-28 01:33:59 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-28 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-28 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-28 01:33:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-28 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-28 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-28 01:34:04 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-28 01:34:04 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-28 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-28 01:34:04 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-28 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-28 01:34:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-28 01:34:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QYm1kjtMp_/ea_profile.json
* 2023-09-28 01:34:10 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QYm1kjtMp_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-28 01:34:10 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-29 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-29 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-29 01:33:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-29 01:33:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-29 01:33:49 (4229) [INFO] 
* 2023-09-29 01:33:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-29 01:33:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-29 01:33:49 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-29 01:33:49 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-29 01:33:49 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-29 01:33:49 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-29 01:33:49 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-29 01:33:49 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-29 01:33:49 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-29 01:33:50 (4259) [INFO] 
* 2023-09-29 01:33:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-29 01:33:50 (4229) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-29 01:34:10 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-29 01:34:10 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-29 01:34:10 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-29 01:34:10 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-29 01:34:10 (4242) [INFO] Trying other mirror.
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-29 01:34:10 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-29 01:34:10 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-29 01:34:10 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-29 01:34:10 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-29 01:34:10 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-29 01:34:10 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-29 01:34:10 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-29 01:34:10 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-29 01:34:10 (4242) [INFO]         or
* 2023-09-29 01:34:10 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-29 01:34:10 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-29 01:34:10 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-29 01:34:10 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-29 01:34:10 (4242) [INFO]         compromise:
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-29 01:34:10 (4242) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-29 01:34:10 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-29 01:34:10 (4259) [INFO] 
* 2023-09-29 01:34:10 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-29 01:34:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-29 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-29 01:34:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-29 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-29 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-29 01:34:11 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-29 01:34:11 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-29 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-29 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-29 01:34:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-29 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-29 01:34:11 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-29 01:34:14 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-29 01:34:14 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-29 01:34:14 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-29 01:34:14 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-29 01:34:14 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-29 01:34:14 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-29 01:34:14 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UqdkD5TSed/ea_profile.json
* 2023-09-29 01:34:18 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UqdkD5TSed/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-29 01:34:18 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-30 01:34:27 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-09-30 01:34:27 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-09-30 01:34:27 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-30 01:34:27 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-30 01:34:27 (4229) [INFO] 
* 2023-09-30 01:34:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-30 01:34:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-09-30 01:34:28 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-09-30 01:34:28 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-09-30 01:34:28 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-09-30 01:34:28 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-09-30 01:34:28 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-09-30 01:34:28 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-09-30 01:34:28 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-09-30 01:34:28 (4259) [INFO] 
* 2023-09-30 01:34:28 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-30 01:34:28 (4229) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-09-30 01:34:41 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-09-30 01:34:41 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-09-30 01:34:41 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-09-30 01:34:41 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-30 01:34:41 (4242) [INFO] Trying other mirror.
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-09-30 01:34:41 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-30 01:34:41 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-30 01:34:41 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-30 01:34:41 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-30 01:34:41 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-30 01:34:41 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-30 01:34:41 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-30 01:34:41 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-09-30 01:34:41 (4242) [INFO]         or
* 2023-09-30 01:34:41 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-30 01:34:41 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-30 01:34:41 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-30 01:34:41 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-30 01:34:41 (4242) [INFO]         compromise:
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-09-30 01:34:41 (4242) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-09-30 01:34:41 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-30 01:34:41 (4259) [INFO] 
* 2023-09-30 01:34:41 (4242) [INFO] Is this ok [y/N]: 
* 2023-09-30 01:34:41 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-30 01:34:41 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-30 01:34:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-09-30 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-09-30 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-09-30 01:34:42 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-09-30 01:34:42 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-09-30 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-09-30 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-09-30 01:34:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-09-30 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-09-30 01:34:42 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-09-30 01:34:45 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-30 01:34:45 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-09-30 01:34:45 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-30 01:34:45 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-09-30 01:34:45 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-09-30 01:34:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-30 01:34:45 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5kez52gfyk/ea_profile.json
* 2023-09-30 01:34:48 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5kez52gfyk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-09-30 01:34:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-01 01:34:34 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-01 01:34:36 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-01 01:34:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-01 01:34:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-01 01:34:36 (4229) [INFO] 
* 2023-10-01 01:34:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-01 01:34:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-01 01:34:36 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-01 01:34:36 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-01 01:34:36 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-01 01:34:36 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-01 01:34:36 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-01 01:34:36 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-01 01:34:36 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-01 01:34:36 (4259) [INFO] 
* 2023-10-01 01:34:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-01 01:34:36 (4229) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-01 01:34:48 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-01 01:34:48 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-01 01:34:48 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-01 01:34:48 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-01 01:34:48 (4242) [INFO] Trying other mirror.
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-01 01:34:48 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-01 01:34:48 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-01 01:34:48 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-01 01:34:48 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-01 01:34:48 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-01 01:34:48 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-01 01:34:48 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-01 01:34:48 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-01 01:34:48 (4242) [INFO]         or
* 2023-10-01 01:34:48 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-01 01:34:48 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-01 01:34:48 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-01 01:34:48 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-01 01:34:48 (4242) [INFO]         compromise:
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-01 01:34:48 (4242) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-01 01:34:48 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-01 01:34:48 (4259) [INFO] 
* 2023-10-01 01:34:48 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-01 01:34:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-01 01:34:48 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-01 01:34:50 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-01 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-01 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-01 01:34:50 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-01 01:34:50 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-01 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-01 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-01 01:34:50 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-01 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-01 01:34:50 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-01 01:34:54 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-01 01:34:54 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-01 01:34:54 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-01 01:34:54 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-01 01:34:54 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-01 01:34:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-01 01:34:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2_TOREYRHO/ea_profile.json
* 2023-10-01 01:34:58 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2_TOREYRHO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-01 01:34:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-02 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-02 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-02 01:33:48 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-02 01:33:48 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-02 01:33:48 (4229) [INFO] 
* 2023-10-02 01:33:48 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-02 01:33:48 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-02 01:33:48 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-02 01:33:48 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-02 01:33:48 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-02 01:33:48 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-02 01:33:48 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-02 01:33:48 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-02 01:33:48 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-02 01:33:48 (4259) [INFO] 
* 2023-10-02 01:33:48 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-02 01:33:48 (4229) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-02 01:34:02 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-02 01:34:02 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-02 01:34:02 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-02 01:34:02 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-02 01:34:02 (4242) [INFO] Trying other mirror.
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-02 01:34:02 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-02 01:34:02 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-02 01:34:02 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-02 01:34:02 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-02 01:34:02 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-02 01:34:02 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-02 01:34:02 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-02 01:34:02 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-02 01:34:02 (4242) [INFO]         or
* 2023-10-02 01:34:02 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-02 01:34:02 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-02 01:34:02 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-02 01:34:02 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-02 01:34:02 (4242) [INFO]         compromise:
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-02 01:34:02 (4242) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-02 01:34:02 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-02 01:34:02 (4259) [INFO] 
* 2023-10-02 01:34:02 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-02 01:34:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-02 01:34:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-02 01:34:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-02 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-02 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-02 01:34:03 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-02 01:34:03 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-02 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-02 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-02 01:34:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-02 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-02 01:34:03 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-02 01:34:06 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-02 01:34:06 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-02 01:34:06 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-02 01:34:06 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-02 01:34:06 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-02 01:34:07 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-02 01:34:07 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dIYSwTCw_Q/ea_profile.json
* 2023-10-02 01:34:12 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dIYSwTCw_Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-02 01:34:12 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-03 01:35:21 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-03 01:35:22 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-03 01:35:22 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-03 01:35:22 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-03 01:35:22 (4229) [INFO] 
* 2023-10-03 01:35:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-03 01:35:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-03 01:35:22 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-03 01:35:22 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-03 01:35:22 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-03 01:35:22 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-03 01:35:22 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-03 01:35:22 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-03 01:35:22 (4242) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2023-10-03 01:35:22 (4259) [INFO] 
* 2023-10-03 01:35:22 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-03 01:35:22 (4229) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-03 01:35:31 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-03 01:35:31 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-03 01:35:31 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-03 01:35:31 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-03 01:35:31 (4242) [INFO] Trying other mirror.
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-03 01:35:31 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-03 01:35:31 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-03 01:35:31 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-03 01:35:31 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-03 01:35:31 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-03 01:35:31 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-03 01:35:31 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-03 01:35:31 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-03 01:35:31 (4242) [INFO]         or
* 2023-10-03 01:35:31 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-03 01:35:31 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-03 01:35:31 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-03 01:35:31 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-03 01:35:31 (4242) [INFO]         compromise:
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-03 01:35:31 (4242) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-03 01:35:31 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-03 01:35:31 (4259) [INFO] 
* 2023-10-03 01:35:31 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-03 01:35:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-03 01:35:31 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-03 01:35:32 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-03 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-03 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-03 01:35:32 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-03 01:35:32 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-03 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-03 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-03 01:35:32 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-03 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-03 01:35:32 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-03 01:35:36 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-03 01:35:36 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-03 01:35:36 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-03 01:35:36 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-03 01:35:36 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-03 01:35:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-03 01:35:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8_lTq43WmA/ea_profile.json
* 2023-10-03 01:35:40 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8_lTq43WmA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-03 01:35:40 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-04 01:34:38 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-04 01:34:38 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-04 01:34:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-04 01:34:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-04 01:34:38 (4229) [INFO] 
* 2023-10-04 01:34:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-04 01:34:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-04 01:34:39 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-04 01:34:39 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-04 01:34:39 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-04 01:34:39 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-04 01:34:39 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-04 01:34:39 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-04 01:34:39 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-04 01:34:39 (4259) [INFO] 
* 2023-10-04 01:34:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-04 01:34:39 (4229) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-04 01:34:54 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-04 01:34:54 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-04 01:34:54 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-04 01:34:54 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-04 01:34:54 (4242) [INFO] Trying other mirror.
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-04 01:34:54 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-04 01:34:54 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-04 01:34:54 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-04 01:34:54 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-04 01:34:54 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-04 01:34:54 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-04 01:34:54 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-04 01:34:54 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-04 01:34:54 (4242) [INFO]         or
* 2023-10-04 01:34:54 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-04 01:34:54 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-04 01:34:54 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-04 01:34:54 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-04 01:34:54 (4242) [INFO]         compromise:
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-04 01:34:54 (4242) [INFO] 
* 2023-10-04 01:34:54 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-04 01:34:54 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-04 01:34:55 (4259) [INFO] 
* 2023-10-04 01:34:55 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-04 01:34:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-04 01:34:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-04 01:34:56 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-04 01:34:56 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-04 01:34:56 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-04 01:34:56 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-04 01:34:56 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-04 01:34:56 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-04 01:34:56 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-04 01:34:56 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-04 01:34:56 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-04 01:34:56 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-04 01:35:02 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-04 01:35:02 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-04 01:35:02 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-04 01:35:02 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-04 01:35:03 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-04 01:35:03 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-04 01:35:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6IpSICgPwf/ea_profile.json
* 2023-10-04 01:35:11 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6IpSICgPwf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-04 01:35:11 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-05 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-05 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-05 01:33:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-05 01:33:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-05 01:33:36 (4229) [INFO] 
* 2023-10-05 01:33:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-05 01:33:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-05 01:33:37 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-05 01:33:37 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-05 01:33:37 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-05 01:33:37 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-05 01:33:37 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-05 01:33:37 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-05 01:33:37 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-05 01:33:37 (4259) [INFO] 
* 2023-10-05 01:33:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-05 01:33:37 (4229) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-05 01:33:49 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-05 01:33:49 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-05 01:33:49 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-05 01:33:49 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-05 01:33:49 (4242) [INFO] Trying other mirror.
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-05 01:33:49 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-05 01:33:49 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-05 01:33:49 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-05 01:33:49 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-05 01:33:49 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-05 01:33:49 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-05 01:33:49 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-05 01:33:49 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-05 01:33:49 (4242) [INFO]         or
* 2023-10-05 01:33:49 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-05 01:33:49 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-05 01:33:49 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-05 01:33:49 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-05 01:33:49 (4242) [INFO]         compromise:
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-05 01:33:49 (4242) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-05 01:33:49 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-05 01:33:49 (4259) [INFO] 
* 2023-10-05 01:33:49 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-05 01:33:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-05 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-05 01:33:50 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-05 01:33:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-05 01:33:50 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-05 01:33:50 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-05 01:33:50 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-05 01:33:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-05 01:33:50 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-05 01:33:50 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-05 01:33:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-05 01:33:50 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-05 01:33:54 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-05 01:33:54 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-05 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-05 01:33:54 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-05 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-05 01:33:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-05 01:33:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aF4Enk5x70/ea_profile.json
* 2023-10-05 01:34:00 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aF4Enk5x70/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-05 01:34:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-06 01:33:41 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-06 01:33:41 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-06 01:33:41 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-06 01:33:41 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-06 01:33:41 (4229) [INFO] 
* 2023-10-06 01:33:41 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-06 01:33:42 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-06 01:33:42 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-06 01:33:42 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-06 01:33:42 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-06 01:33:42 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-06 01:33:42 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-06 01:33:42 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-06 01:33:42 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-06 01:33:42 (4259) [INFO] 
* 2023-10-06 01:33:42 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-06 01:33:42 (4229) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-06 01:33:51 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-06 01:33:51 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-06 01:33:51 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-06 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-06 01:33:51 (4242) [INFO] Trying other mirror.
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-06 01:33:51 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-06 01:33:51 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-06 01:33:51 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-06 01:33:51 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-06 01:33:51 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-06 01:33:51 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-06 01:33:51 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-06 01:33:51 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-06 01:33:51 (4242) [INFO]         or
* 2023-10-06 01:33:51 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-06 01:33:51 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-06 01:33:51 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-06 01:33:51 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-06 01:33:51 (4242) [INFO]         compromise:
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-06 01:33:51 (4242) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-06 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-06 01:33:51 (4259) [INFO] 
* 2023-10-06 01:33:51 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-06 01:33:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-06 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-06 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-06 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-06 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-06 01:33:52 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-06 01:33:52 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-06 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-06 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-06 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-06 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-06 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-06 01:33:55 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-06 01:33:55 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-06 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-06 01:33:55 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-06 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-06 01:33:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-06 01:33:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iLIjjG_nDo/ea_profile.json
* 2023-10-06 01:33:58 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iLIjjG_nDo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-06 01:33:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-07 01:35:20 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-07 01:35:21 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-07 01:35:21 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-07 01:35:21 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-07 01:35:21 (4229) [INFO] 
* 2023-10-07 01:35:21 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-07 01:35:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-07 01:35:22 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-07 01:35:22 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-07 01:35:22 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-07 01:35:22 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-07 01:35:22 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-07 01:35:22 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-07 01:35:22 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-07 01:35:22 (4259) [INFO] 
* 2023-10-07 01:35:22 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-07 01:35:22 (4229) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-07 01:35:37 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-07 01:35:37 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-07 01:35:37 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-07 01:35:37 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-07 01:35:37 (4242) [INFO] Trying other mirror.
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-07 01:35:37 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-07 01:35:37 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-07 01:35:37 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-07 01:35:37 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-07 01:35:37 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-07 01:35:37 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-07 01:35:37 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-07 01:35:37 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-07 01:35:37 (4242) [INFO]         or
* 2023-10-07 01:35:37 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-07 01:35:37 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-07 01:35:37 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-07 01:35:37 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-07 01:35:37 (4242) [INFO]         compromise:
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-07 01:35:37 (4242) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-07 01:35:37 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-07 01:35:37 (4259) [INFO] 
* 2023-10-07 01:35:37 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-07 01:35:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-07 01:35:37 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-07 01:35:39 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-07 01:35:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-07 01:35:39 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-07 01:35:39 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-07 01:35:39 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-07 01:35:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-07 01:35:39 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-07 01:35:39 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-07 01:35:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-07 01:35:39 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-07 01:35:43 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-07 01:35:43 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-07 01:35:43 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-07 01:35:43 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-07 01:35:43 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-07 01:35:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-07 01:35:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YLfRSMM6ox/ea_profile.json
* 2023-10-07 01:35:47 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YLfRSMM6ox/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-07 01:35:47 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-08 01:34:56 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-08 01:34:57 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-08 01:34:57 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-08 01:34:57 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-08 01:34:57 (4229) [INFO] 
* 2023-10-08 01:34:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-08 01:34:57 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-08 01:34:57 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-08 01:34:57 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-08 01:34:57 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-08 01:34:57 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-08 01:34:57 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-08 01:34:57 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-08 01:34:57 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-08 01:34:57 (4259) [INFO] 
* 2023-10-08 01:34:57 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-08 01:34:57 (4229) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-08 01:35:07 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-08 01:35:07 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-08 01:35:07 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-08 01:35:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-08 01:35:07 (4242) [INFO] Trying other mirror.
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-08 01:35:07 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-08 01:35:07 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-08 01:35:07 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-08 01:35:07 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-08 01:35:07 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-08 01:35:07 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-08 01:35:07 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-08 01:35:07 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-08 01:35:07 (4242) [INFO]         or
* 2023-10-08 01:35:07 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-08 01:35:07 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-08 01:35:07 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-08 01:35:07 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-08 01:35:07 (4242) [INFO]         compromise:
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-08 01:35:07 (4242) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-08 01:35:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-08 01:35:07 (4259) [INFO] 
* 2023-10-08 01:35:07 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-08 01:35:07 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-08 01:35:07 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-08 01:35:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-08 01:35:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-08 01:35:08 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-08 01:35:08 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-08 01:35:08 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-08 01:35:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-08 01:35:08 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-08 01:35:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-08 01:35:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-08 01:35:08 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-08 01:35:11 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-08 01:35:11 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-08 01:35:11 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-08 01:35:11 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-08 01:35:11 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-08 01:35:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-08 01:35:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ScEgvgDXCR/ea_profile.json
* 2023-10-08 01:35:17 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ScEgvgDXCR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-08 01:35:17 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-09 01:33:38 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-09 01:33:39 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-09 01:33:39 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-09 01:33:39 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-09 01:33:39 (4229) [INFO] 
* 2023-10-09 01:33:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-09 01:33:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-09 01:33:39 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-09 01:33:39 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-09 01:33:39 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-09 01:33:39 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-09 01:33:39 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-09 01:33:39 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-09 01:33:39 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-09 01:33:39 (4259) [INFO] 
* 2023-10-09 01:33:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-09 01:33:39 (4229) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-09 01:33:48 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-09 01:33:48 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-09 01:33:48 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-09 01:33:48 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-09 01:33:48 (4242) [INFO] Trying other mirror.
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-09 01:33:48 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-09 01:33:48 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-09 01:33:48 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-09 01:33:48 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-09 01:33:48 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-09 01:33:48 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-09 01:33:48 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-09 01:33:48 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-09 01:33:48 (4242) [INFO]         or
* 2023-10-09 01:33:48 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-09 01:33:48 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-09 01:33:48 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-09 01:33:48 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-09 01:33:48 (4242) [INFO]         compromise:
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-09 01:33:48 (4242) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-09 01:33:48 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-09 01:33:48 (4259) [INFO] 
* 2023-10-09 01:33:48 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-09 01:33:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-09 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-09 01:33:49 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-09 01:33:49 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-09 01:33:49 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-09 01:33:49 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-09 01:33:49 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-09 01:33:49 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-09 01:33:49 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-09 01:33:49 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-09 01:33:49 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-09 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-09 01:33:53 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-09 01:33:53 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-09 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-09 01:33:53 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-09 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-09 01:33:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-09 01:33:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jby8Nrt8fq/ea_profile.json
* 2023-10-09 01:33:57 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jby8Nrt8fq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-09 01:33:57 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-10 01:34:52 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-10 01:34:53 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-10 01:34:53 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-10 01:34:53 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-10 01:34:53 (4229) [INFO] 
* 2023-10-10 01:34:53 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-10 01:34:53 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-10 01:34:53 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-10 01:34:53 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-10 01:34:53 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-10 01:34:53 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-10 01:34:53 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-10 01:34:53 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-10 01:34:53 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-10 01:34:53 (4259) [INFO] 
* 2023-10-10 01:34:53 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-10 01:34:53 (4229) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-10 01:35:14 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-10 01:35:14 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-10 01:35:14 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-10 01:35:14 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-10 01:35:14 (4242) [INFO] Trying other mirror.
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-10 01:35:14 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-10 01:35:14 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-10 01:35:14 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-10 01:35:14 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-10 01:35:14 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-10 01:35:14 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-10 01:35:14 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-10 01:35:14 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-10 01:35:14 (4242) [INFO]         or
* 2023-10-10 01:35:14 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-10 01:35:14 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-10 01:35:14 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-10 01:35:14 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-10 01:35:14 (4242) [INFO]         compromise:
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-10 01:35:14 (4242) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-10 01:35:14 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-10 01:35:14 (4259) [INFO] 
* 2023-10-10 01:35:14 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-10 01:35:14 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-10 01:35:14 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-10 01:35:15 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-10 01:35:15 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-10 01:35:15 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-10 01:35:15 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-10 01:35:15 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-10 01:35:15 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-10 01:35:15 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-10 01:35:15 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-10 01:35:15 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-10 01:35:15 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-10 01:35:39 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-10 01:35:39 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-10 01:35:39 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-10 01:35:39 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-10 01:35:39 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-10 01:35:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-10 01:35:39 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ax6sSnDnZe/ea_profile.json
* 2023-10-10 01:35:56 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ax6sSnDnZe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-10 01:35:56 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-11 01:33:34 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-11 01:33:34 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-11 01:33:34 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-11 01:33:34 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-11 01:33:34 (4229) [INFO] 
* 2023-10-11 01:33:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-11 01:33:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-11 01:33:35 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-11 01:33:35 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-11 01:33:35 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-11 01:33:35 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-11 01:33:35 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-11 01:33:35 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-11 01:33:35 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-11 01:33:35 (4259) [INFO] 
* 2023-10-11 01:33:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-11 01:33:35 (4229) [INFO] 
* 2023-10-11 01:34:21 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml.asc: [Errno 12] Timeout on http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml.asc: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-10-11 01:34:21 (4242) [INFO] Trying other mirror.
* 2023-10-11 01:34:23 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-11 01:34:23 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-11 01:34:23 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-11 01:34:23 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-11 01:34:23 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-11 01:34:23 (4242) [INFO] Trying other mirror.
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-11 01:34:23 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-11 01:34:23 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-11 01:34:23 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-11 01:34:23 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-11 01:34:23 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-11 01:34:23 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-11 01:34:23 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-11 01:34:23 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-11 01:34:23 (4242) [INFO]         or
* 2023-10-11 01:34:23 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-11 01:34:23 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-11 01:34:23 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-11 01:34:23 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-11 01:34:23 (4242) [INFO]         compromise:
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-11 01:34:23 (4242) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-11 01:34:23 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-11 01:34:23 (4259) [INFO] 
* 2023-10-11 01:34:23 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-11 01:34:23 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-11 01:34:23 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-11 01:34:26 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-11 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-11 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-11 01:34:26 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-11 01:34:26 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-11 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-11 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-11 01:34:26 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-11 01:34:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-11 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-11 01:34:31 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-11 01:34:31 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-11 01:34:31 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-11 01:34:31 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-11 01:34:31 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-11 01:34:31 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-11 01:34:32 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9pUCjxpu6q/ea_profile.json
* 2023-10-11 01:34:36 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9pUCjxpu6q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-11 01:34:36 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-12 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-12 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-12 01:33:46 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-12 01:33:46 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-12 01:33:46 (4229) [INFO] 
* 2023-10-12 01:33:46 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-12 01:33:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-12 01:33:47 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-12 01:33:47 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-12 01:33:47 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-12 01:33:47 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-12 01:33:47 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-12 01:33:47 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-12 01:33:47 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-12 01:33:47 (4259) [INFO] 
* 2023-10-12 01:33:47 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-12 01:33:47 (4229) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-12 01:33:59 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-12 01:33:59 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-12 01:33:59 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-12 01:33:59 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-12 01:33:59 (4242) [INFO] Trying other mirror.
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-12 01:33:59 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-12 01:33:59 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-12 01:33:59 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-12 01:33:59 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-12 01:33:59 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-12 01:33:59 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-12 01:33:59 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-12 01:33:59 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-12 01:33:59 (4242) [INFO]         or
* 2023-10-12 01:33:59 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-12 01:33:59 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-12 01:33:59 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-12 01:33:59 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-12 01:33:59 (4242) [INFO]         compromise:
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-12 01:33:59 (4242) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-12 01:33:59 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-12 01:33:59 (4259) [INFO] 
* 2023-10-12 01:33:59 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-12 01:33:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-12 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-12 01:34:00 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-12 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-12 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-12 01:34:00 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-12 01:34:00 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-12 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-12 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-12 01:34:00 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-12 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-12 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-12 01:34:04 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-12 01:34:04 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-12 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-12 01:34:04 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-12 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-12 01:34:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-12 01:34:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/926aIt6Uln/ea_profile.json
* 2023-10-12 01:34:12 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/926aIt6Uln/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-12 01:34:12 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-13 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-13 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-13 01:33:52 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-13 01:33:52 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-13 01:33:52 (4229) [INFO] 
* 2023-10-13 01:33:52 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-13 01:33:52 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-13 01:33:52 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-13 01:33:52 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-13 01:33:52 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-13 01:33:52 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-13 01:33:52 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-13 01:33:52 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-13 01:33:52 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-13 01:33:52 (4259) [INFO] 
* 2023-10-13 01:33:52 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-13 01:33:52 (4229) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-13 01:34:04 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-13 01:34:04 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-13 01:34:04 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-13 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-13 01:34:04 (4242) [INFO] Trying other mirror.
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-13 01:34:04 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-13 01:34:04 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-13 01:34:04 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-13 01:34:04 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-13 01:34:04 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-13 01:34:04 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-13 01:34:04 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-13 01:34:04 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-13 01:34:04 (4242) [INFO]         or
* 2023-10-13 01:34:04 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-13 01:34:04 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-13 01:34:04 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-13 01:34:04 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-13 01:34:04 (4242) [INFO]         compromise:
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-13 01:34:04 (4242) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-13 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-13 01:34:04 (4259) [INFO] 
* 2023-10-13 01:34:04 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-13 01:34:04 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-13 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-13 01:34:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-13 01:34:06 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-13 01:34:06 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-13 01:34:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-13 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-13 01:34:06 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-13 01:34:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-13 01:34:10 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-13 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-13 01:34:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-13 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-13 01:34:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-13 01:34:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/muWS1NqFnx/ea_profile.json
* 2023-10-13 01:34:15 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/muWS1NqFnx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-13 01:34:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-14 01:35:17 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-14 01:35:18 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-14 01:35:18 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-14 01:35:18 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-14 01:35:18 (4229) [INFO] 
* 2023-10-14 01:35:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-14 01:35:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-14 01:35:18 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-14 01:35:18 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-14 01:35:18 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-14 01:35:18 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-14 01:35:18 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-14 01:35:18 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-14 01:35:18 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-14 01:35:18 (4259) [INFO] 
* 2023-10-14 01:35:18 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-14 01:35:18 (4229) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-14 01:35:31 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-14 01:35:31 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-14 01:35:31 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-14 01:35:31 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-14 01:35:31 (4242) [INFO] Trying other mirror.
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-14 01:35:31 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-14 01:35:31 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-14 01:35:31 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-14 01:35:31 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-14 01:35:31 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-14 01:35:31 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-14 01:35:31 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-14 01:35:31 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-14 01:35:31 (4242) [INFO]         or
* 2023-10-14 01:35:31 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-14 01:35:31 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-14 01:35:31 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-14 01:35:31 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-14 01:35:31 (4242) [INFO]         compromise:
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-14 01:35:31 (4242) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-14 01:35:31 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-14 01:35:31 (4259) [INFO] 
* 2023-10-14 01:35:31 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-14 01:35:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-14 01:35:31 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-14 01:35:32 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-14 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-14 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-14 01:35:32 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-14 01:35:32 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-14 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-14 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-14 01:35:32 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-14 01:35:32 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-14 01:35:32 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-14 01:35:36 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-14 01:35:36 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-14 01:35:36 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-14 01:35:36 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-14 01:35:36 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-14 01:35:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-14 01:35:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TdBjWVnUya/ea_profile.json
* 2023-10-14 01:35:39 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TdBjWVnUya/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-14 01:35:39 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-15 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-15 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-15 01:34:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-15 01:34:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-15 01:34:49 (4229) [INFO] 
* 2023-10-15 01:34:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-15 01:34:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-15 01:34:50 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-15 01:34:50 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-15 01:34:50 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-15 01:34:50 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-15 01:34:50 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-15 01:34:50 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-15 01:34:50 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-15 01:34:50 (4259) [INFO] 
* 2023-10-15 01:34:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-15 01:34:50 (4229) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-15 01:35:04 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-15 01:35:04 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-15 01:35:04 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-15 01:35:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-15 01:35:04 (4242) [INFO] Trying other mirror.
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-15 01:35:04 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-15 01:35:04 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-15 01:35:04 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-15 01:35:04 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-15 01:35:04 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-15 01:35:04 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-15 01:35:04 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-15 01:35:04 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-15 01:35:04 (4242) [INFO]         or
* 2023-10-15 01:35:04 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-15 01:35:04 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-15 01:35:04 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-15 01:35:04 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-15 01:35:04 (4242) [INFO]         compromise:
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-15 01:35:04 (4242) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-15 01:35:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-15 01:35:04 (4259) [INFO] 
* 2023-10-15 01:35:04 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-15 01:35:04 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-15 01:35:04 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-15 01:35:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-15 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-15 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-15 01:35:06 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-15 01:35:06 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-15 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-15 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-15 01:35:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-15 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-15 01:35:06 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-15 01:35:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-15 01:35:10 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-15 01:35:10 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-15 01:35:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-15 01:35:10 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-15 01:35:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-15 01:35:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lLRBrZyFl9/ea_profile.json
* 2023-10-15 01:35:15 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lLRBrZyFl9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-15 01:35:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-16 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-16 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-16 01:33:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-16 01:33:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-16 01:33:40 (4229) [INFO] 
* 2023-10-16 01:33:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-16 01:33:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-16 01:33:41 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-16 01:33:41 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-16 01:33:41 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-16 01:33:41 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-16 01:33:41 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-16 01:33:41 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-16 01:33:41 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-16 01:33:41 (4259) [INFO] 
* 2023-10-16 01:33:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-16 01:33:41 (4229) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-16 01:33:51 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-16 01:33:51 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-16 01:33:51 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-16 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-16 01:33:51 (4242) [INFO] Trying other mirror.
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-16 01:33:51 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-16 01:33:51 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-16 01:33:51 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-16 01:33:51 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-16 01:33:51 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-16 01:33:51 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-16 01:33:51 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-16 01:33:51 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-16 01:33:51 (4242) [INFO]         or
* 2023-10-16 01:33:51 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-16 01:33:51 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-16 01:33:51 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-16 01:33:51 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-16 01:33:51 (4242) [INFO]         compromise:
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-16 01:33:51 (4242) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-16 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-16 01:33:51 (4259) [INFO] 
* 2023-10-16 01:33:51 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-16 01:33:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-16 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-16 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-16 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-16 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-16 01:33:52 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-16 01:33:52 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-16 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-16 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-16 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-16 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-16 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-16 01:33:56 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-16 01:33:56 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-16 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-16 01:33:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-16 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-16 01:33:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-16 01:33:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3xHBSxtRi_/ea_profile.json
* 2023-10-16 01:34:01 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3xHBSxtRi_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-16 01:34:01 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-17 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-17 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-17 01:33:43 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-17 01:33:43 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-17 01:33:43 (4229) [INFO] 
* 2023-10-17 01:33:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-17 01:33:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-17 01:33:43 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-17 01:33:43 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-17 01:33:43 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-17 01:33:43 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-17 01:33:43 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-17 01:33:43 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-17 01:33:43 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-17 01:33:43 (4259) [INFO] 
* 2023-10-17 01:33:43 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-17 01:33:43 (4229) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-17 01:33:58 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-17 01:33:58 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-17 01:33:58 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-17 01:33:58 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-17 01:33:58 (4242) [INFO] Trying other mirror.
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-17 01:33:58 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-17 01:33:58 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-17 01:33:58 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-17 01:33:58 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-17 01:33:58 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-17 01:33:58 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-17 01:33:58 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-17 01:33:58 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-17 01:33:58 (4242) [INFO]         or
* 2023-10-17 01:33:58 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-17 01:33:58 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-17 01:33:58 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-17 01:33:58 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-17 01:33:58 (4242) [INFO]         compromise:
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-17 01:33:58 (4242) [INFO] 
* 2023-10-17 01:33:58 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-17 01:33:58 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-17 01:33:58 (4259) [INFO] 
* 2023-10-17 01:33:59 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-17 01:33:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-17 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-17 01:34:00 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-17 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-17 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-17 01:34:00 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-17 01:34:00 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-17 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-17 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-17 01:34:00 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-17 01:34:00 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-17 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-17 01:34:04 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-17 01:34:04 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-17 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-17 01:34:05 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-17 01:34:05 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-17 01:34:05 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-17 01:34:05 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RUNnHMj8qN/ea_profile.json
* 2023-10-17 01:34:09 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RUNnHMj8qN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-17 01:34:09 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-18 01:33:37 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-18 01:33:37 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-18 01:33:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-18 01:33:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-18 01:33:37 (4229) [INFO] 
* 2023-10-18 01:33:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-18 01:33:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-18 01:33:38 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-18 01:33:38 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-18 01:33:38 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-18 01:33:38 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-18 01:33:38 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-18 01:33:38 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-18 01:33:38 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-18 01:33:38 (4259) [INFO] 
* 2023-10-18 01:33:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-18 01:33:38 (4229) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-18 01:33:52 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-18 01:33:52 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-18 01:33:52 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-18 01:33:52 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-18 01:33:52 (4242) [INFO] Trying other mirror.
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-18 01:33:52 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-18 01:33:52 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-18 01:33:52 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-18 01:33:52 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-18 01:33:52 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-18 01:33:52 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-18 01:33:52 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-18 01:33:52 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-18 01:33:52 (4242) [INFO]         or
* 2023-10-18 01:33:52 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-18 01:33:52 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-18 01:33:52 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-18 01:33:52 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-18 01:33:52 (4242) [INFO]         compromise:
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-18 01:33:52 (4242) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-18 01:33:52 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-18 01:33:52 (4259) [INFO] 
* 2023-10-18 01:33:52 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-18 01:33:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-18 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-18 01:33:53 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-18 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-18 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-18 01:33:53 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-18 01:33:53 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-18 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-18 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-18 01:33:53 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-18 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-18 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-18 01:33:56 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-18 01:33:56 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-18 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-18 01:33:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-18 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-18 01:33:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-18 01:33:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PngN43RUks/ea_profile.json
* 2023-10-18 01:34:00 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PngN43RUks/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-18 01:34:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-19 01:34:29 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-19 01:34:30 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-19 01:34:30 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-19 01:34:30 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-19 01:34:30 (4229) [INFO] 
* 2023-10-19 01:34:30 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-19 01:34:30 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-19 01:34:30 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-19 01:34:30 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-19 01:34:30 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-19 01:34:30 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-19 01:34:30 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-19 01:34:30 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-19 01:34:30 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-19 01:34:30 (4259) [INFO] 
* 2023-10-19 01:34:30 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-19 01:34:30 (4229) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-19 01:34:43 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-19 01:34:43 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-19 01:34:43 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-19 01:34:43 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-19 01:34:43 (4242) [INFO] Trying other mirror.
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-19 01:34:43 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-19 01:34:43 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-19 01:34:43 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-19 01:34:43 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-19 01:34:43 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-19 01:34:43 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-19 01:34:43 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-19 01:34:43 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-19 01:34:43 (4242) [INFO]         or
* 2023-10-19 01:34:43 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-19 01:34:43 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-19 01:34:43 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-19 01:34:43 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-19 01:34:43 (4242) [INFO]         compromise:
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-19 01:34:43 (4242) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-19 01:34:43 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-19 01:34:43 (4259) [INFO] 
* 2023-10-19 01:34:43 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-19 01:34:43 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-19 01:34:43 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-19 01:34:45 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-19 01:34:45 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-19 01:34:45 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-19 01:34:45 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-19 01:34:45 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-19 01:34:45 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-19 01:34:45 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-19 01:34:45 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-19 01:34:45 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-19 01:34:45 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-19 01:34:49 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-19 01:34:49 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-19 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-19 01:34:49 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-19 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-19 01:34:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-19 01:34:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1sVHyLjQBM/ea_profile.json
* 2023-10-19 01:34:53 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1sVHyLjQBM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-19 01:34:53 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-20 01:33:41 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-20 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-20 01:33:42 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-20 01:33:42 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-20 01:33:42 (4229) [INFO] 
* 2023-10-20 01:33:42 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-20 01:33:42 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-20 01:33:42 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-20 01:33:42 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-20 01:33:42 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-20 01:33:42 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-20 01:33:42 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-20 01:33:42 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-20 01:33:42 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-20 01:33:42 (4259) [INFO] 
* 2023-10-20 01:33:42 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-20 01:33:42 (4229) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-20 01:33:51 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-20 01:33:51 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-20 01:33:51 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-20 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-20 01:33:51 (4242) [INFO] Trying other mirror.
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-20 01:33:51 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-20 01:33:51 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-20 01:33:51 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-20 01:33:51 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-20 01:33:51 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-20 01:33:51 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-20 01:33:51 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-20 01:33:51 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-20 01:33:51 (4242) [INFO]         or
* 2023-10-20 01:33:51 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-20 01:33:51 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-20 01:33:51 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-20 01:33:51 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-20 01:33:51 (4242) [INFO]         compromise:
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-20 01:33:51 (4242) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-20 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-20 01:33:51 (4259) [INFO] 
* 2023-10-20 01:33:51 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-20 01:33:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-20 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-20 01:33:53 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-20 01:33:53 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-20 01:33:53 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-20 01:33:53 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-20 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-20 01:33:56 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-20 01:33:56 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-20 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-20 01:33:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-20 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-20 01:33:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-20 01:33:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4xelcxH0Jn/ea_profile.json
* 2023-10-20 01:34:00 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4xelcxH0Jn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-20 01:34:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-21 01:35:21 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-21 01:35:22 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-21 01:35:22 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-21 01:35:22 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-21 01:35:22 (4229) [INFO] 
* 2023-10-21 01:35:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-21 01:35:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-21 01:35:22 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-21 01:35:22 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-21 01:35:22 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-21 01:35:22 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-21 01:35:22 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-21 01:35:22 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-21 01:35:22 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-21 01:35:22 (4259) [INFO] 
* 2023-10-21 01:35:22 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-21 01:35:22 (4229) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-21 01:35:32 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-21 01:35:32 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-21 01:35:32 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-21 01:35:32 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-21 01:35:32 (4242) [INFO] Trying other mirror.
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-21 01:35:32 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-21 01:35:32 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-21 01:35:32 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-21 01:35:32 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-21 01:35:32 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-21 01:35:32 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-21 01:35:32 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-21 01:35:32 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-21 01:35:32 (4242) [INFO]         or
* 2023-10-21 01:35:32 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-21 01:35:32 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-21 01:35:32 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-21 01:35:32 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-21 01:35:32 (4242) [INFO]         compromise:
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-21 01:35:32 (4242) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-21 01:35:32 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-21 01:35:32 (4259) [INFO] 
* 2023-10-21 01:35:32 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-21 01:35:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-21 01:35:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-21 01:35:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-21 01:35:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-21 01:35:33 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-21 01:35:33 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-21 01:35:33 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-21 01:35:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-21 01:35:33 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-21 01:35:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-21 01:35:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-21 01:35:33 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-21 01:35:40 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-21 01:35:40 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-21 01:35:40 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-21 01:35:40 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-21 01:35:40 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-21 01:35:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-21 01:35:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rlAH9NC9WG/ea_profile.json
* 2023-10-21 01:35:46 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rlAH9NC9WG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-21 01:35:46 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-22 01:34:54 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-22 01:34:54 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-22 01:34:54 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-22 01:34:54 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-22 01:34:54 (4229) [INFO] 
* 2023-10-22 01:34:54 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-22 01:34:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-22 01:34:54 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-22 01:34:54 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-22 01:34:54 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-22 01:34:54 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-22 01:34:54 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-22 01:34:54 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-22 01:34:54 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-22 01:34:54 (4259) [INFO] 
* 2023-10-22 01:34:54 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-22 01:34:54 (4229) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-22 01:35:04 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-22 01:35:04 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-22 01:35:04 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-22 01:35:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-22 01:35:04 (4242) [INFO] Trying other mirror.
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-22 01:35:04 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-22 01:35:04 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-22 01:35:04 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-22 01:35:04 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-22 01:35:04 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-22 01:35:04 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-22 01:35:04 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-22 01:35:04 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-22 01:35:04 (4242) [INFO]         or
* 2023-10-22 01:35:04 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-22 01:35:04 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-22 01:35:04 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-22 01:35:04 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-22 01:35:04 (4242) [INFO]         compromise:
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-22 01:35:04 (4242) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-22 01:35:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-22 01:35:04 (4259) [INFO] 
* 2023-10-22 01:35:04 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-22 01:35:04 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-22 01:35:04 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-22 01:35:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-22 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-22 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-22 01:35:06 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-22 01:35:06 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-22 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-22 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-22 01:35:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-22 01:35:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-22 01:35:06 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-22 01:35:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-22 01:35:10 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-22 01:35:10 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-22 01:35:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-22 01:35:10 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-22 01:35:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-22 01:35:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E6Rxf8od0Y/ea_profile.json
* 2023-10-22 01:35:15 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E6Rxf8od0Y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-22 01:35:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-23 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-23 01:34:09 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2023-10-23 01:34:09 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-23 01:34:09 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-23 01:34:09 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-23 01:34:09 (4229) [INFO] 
* 2023-10-23 01:34:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-23 01:34:10 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-23 01:34:10 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-23 01:34:10 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-23 01:34:10 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-23 01:34:10 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-23 01:34:10 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-23 01:34:10 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-23 01:34:10 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-23 01:34:10 (4259) [INFO] 
* 2023-10-23 01:34:10 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-23 01:34:10 (4229) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-23 01:34:23 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-23 01:34:23 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-23 01:34:23 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-23 01:34:23 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-23 01:34:23 (4242) [INFO] Trying other mirror.
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-23 01:34:23 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-23 01:34:23 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-23 01:34:23 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-23 01:34:23 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-23 01:34:23 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-23 01:34:23 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-23 01:34:23 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-23 01:34:23 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-23 01:34:23 (4242) [INFO]         or
* 2023-10-23 01:34:23 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-23 01:34:23 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-23 01:34:23 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-23 01:34:23 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-23 01:34:23 (4242) [INFO]         compromise:
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-23 01:34:23 (4242) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-23 01:34:23 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-23 01:34:23 (4259) [INFO] 
* 2023-10-23 01:34:23 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-23 01:34:23 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-23 01:34:23 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-23 01:34:25 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-23 01:34:25 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-23 01:34:25 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-23 01:34:25 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-23 01:34:25 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-23 01:34:25 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-23 01:34:25 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-23 01:34:25 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-23 01:34:25 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-23 01:34:25 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-23 01:34:33 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-23 01:34:33 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-23 01:34:33 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-23 01:34:33 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-23 01:34:33 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-23 01:34:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-23 01:34:34 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JtLj7c09yF/ea_profile.json
* 2023-10-23 01:34:41 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JtLj7c09yF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-23 01:34:41 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-24 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-24 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-24 01:33:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-24 01:33:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-24 01:33:40 (4229) [INFO] 
* 2023-10-24 01:33:41 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-24 01:33:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-24 01:33:41 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-24 01:33:41 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-24 01:33:41 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-24 01:33:41 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-24 01:33:41 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-24 01:33:41 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-24 01:33:41 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-24 01:33:41 (4259) [INFO] 
* 2023-10-24 01:33:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-24 01:33:41 (4229) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-24 01:33:53 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-24 01:33:53 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-24 01:33:53 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-24 01:33:53 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-24 01:33:53 (4242) [INFO] Trying other mirror.
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-24 01:33:53 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-24 01:33:53 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-24 01:33:53 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-24 01:33:53 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-24 01:33:53 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-24 01:33:53 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-24 01:33:53 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-24 01:33:53 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-24 01:33:53 (4242) [INFO]         or
* 2023-10-24 01:33:53 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-24 01:33:53 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-24 01:33:53 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-24 01:33:53 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-24 01:33:53 (4242) [INFO]         compromise:
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-24 01:33:53 (4242) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-24 01:33:53 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-24 01:33:53 (4259) [INFO] 
* 2023-10-24 01:33:53 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-24 01:33:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-24 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-24 01:33:55 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-24 01:33:55 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-24 01:33:55 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-24 01:33:55 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-24 01:33:55 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-24 01:33:55 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-24 01:33:55 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-24 01:33:55 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-24 01:33:55 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-24 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-24 01:33:59 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-24 01:33:59 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-24 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-24 01:33:59 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-24 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-24 01:33:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-24 01:33:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jHWl7lIFob/ea_profile.json
* 2023-10-24 01:34:03 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jHWl7lIFob/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-24 01:34:03 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-25 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-25 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-10-25 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-25 01:33:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-25 01:33:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-25 01:33:49 (4229) [INFO] 
* 2023-10-25 01:33:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-25 01:33:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-25 01:33:50 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-25 01:33:50 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-25 01:33:50 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-25 01:33:50 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-25 01:33:50 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-25 01:33:50 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-25 01:33:50 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-25 01:33:50 (4259) [INFO] 
* 2023-10-25 01:33:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-25 01:33:50 (4229) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-25 01:34:04 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-25 01:34:04 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-25 01:34:04 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-25 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-25 01:34:04 (4242) [INFO] Trying other mirror.
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-25 01:34:04 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-25 01:34:04 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-25 01:34:04 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-25 01:34:04 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-25 01:34:04 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-25 01:34:04 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-25 01:34:04 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-25 01:34:04 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-25 01:34:04 (4242) [INFO]         or
* 2023-10-25 01:34:04 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-25 01:34:04 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-25 01:34:04 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-25 01:34:04 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-25 01:34:04 (4242) [INFO]         compromise:
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-25 01:34:04 (4242) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-25 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-25 01:34:04 (4259) [INFO] 
* 2023-10-25 01:34:04 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-25 01:34:04 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-25 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-25 01:34:07 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-25 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-25 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-25 01:34:07 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-25 01:34:07 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-25 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-25 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-25 01:34:07 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-25 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-25 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-25 01:34:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-25 01:34:10 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-25 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-25 01:34:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-25 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-25 01:34:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-25 01:34:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o9VSHWBra8/ea_profile.json
* 2023-10-25 01:34:14 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o9VSHWBra8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-25 01:34:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-26 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-26 01:33:58 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-10-26 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-26 01:34:00 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-26 01:34:00 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-26 01:34:00 (4229) [INFO] 
* 2023-10-26 01:34:00 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-26 01:34:00 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-26 01:34:00 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-26 01:34:00 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-26 01:34:00 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-26 01:34:00 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-26 01:34:00 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-26 01:34:00 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-26 01:34:00 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-26 01:34:00 (4259) [INFO] 
* 2023-10-26 01:34:00 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-26 01:34:00 (4229) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-26 01:34:10 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-26 01:34:10 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-26 01:34:10 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-26 01:34:10 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-26 01:34:10 (4242) [INFO] Trying other mirror.
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-26 01:34:10 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-26 01:34:10 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-26 01:34:10 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-26 01:34:10 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-26 01:34:10 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-26 01:34:10 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-26 01:34:10 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-26 01:34:10 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-26 01:34:10 (4242) [INFO]         or
* 2023-10-26 01:34:10 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-26 01:34:10 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-26 01:34:10 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-26 01:34:10 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-26 01:34:10 (4242) [INFO]         compromise:
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-26 01:34:10 (4242) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-26 01:34:10 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-26 01:34:10 (4259) [INFO] 
* 2023-10-26 01:34:10 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-26 01:34:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-26 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-26 01:34:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-26 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-26 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-26 01:34:11 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-26 01:34:11 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-26 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-26 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-26 01:34:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-26 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-26 01:34:11 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-26 01:34:16 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-26 01:34:16 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-26 01:34:16 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-26 01:34:17 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-26 01:34:17 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-26 01:34:17 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-26 01:34:17 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/M2KbPiPvn8/ea_profile.json
* 2023-10-26 01:34:21 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/M2KbPiPvn8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-26 01:34:21 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-27 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-27 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-10-27 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-27 01:33:52 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-27 01:33:52 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-27 01:33:52 (4229) [INFO] 
* 2023-10-27 01:33:52 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-27 01:33:52 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-27 01:33:52 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-27 01:33:52 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-27 01:33:52 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-27 01:33:52 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-27 01:33:52 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-27 01:33:52 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-27 01:33:52 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-27 01:33:52 (4259) [INFO] 
* 2023-10-27 01:33:52 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-27 01:33:52 (4229) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-27 01:34:03 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-27 01:34:03 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-27 01:34:03 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-27 01:34:03 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-27 01:34:03 (4242) [INFO] Trying other mirror.
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-27 01:34:03 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-27 01:34:03 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-27 01:34:03 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-27 01:34:03 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-27 01:34:03 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-27 01:34:03 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-27 01:34:03 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-27 01:34:03 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-27 01:34:03 (4242) [INFO]         or
* 2023-10-27 01:34:03 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-27 01:34:03 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-27 01:34:03 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-27 01:34:03 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-27 01:34:03 (4242) [INFO]         compromise:
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-27 01:34:03 (4242) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-27 01:34:03 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-27 01:34:03 (4259) [INFO] 
* 2023-10-27 01:34:03 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-27 01:34:03 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-27 01:34:03 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-27 01:34:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-27 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-27 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-27 01:34:11 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-27 01:34:11 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-27 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-27 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-27 01:34:11 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-27 01:34:11 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-27 01:34:11 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-27 01:34:15 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-27 01:34:15 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-27 01:34:15 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-27 01:34:15 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-27 01:34:15 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-27 01:34:15 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-27 01:34:15 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7p0z4KX7ug/ea_profile.json
* 2023-10-27 01:34:19 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7p0z4KX7ug/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-27 01:34:19 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-28 01:36:15 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-28 01:36:15 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-10-28 01:36:15 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-28 01:36:15 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-28 01:36:15 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-28 01:36:15 (4229) [INFO] 
* 2023-10-28 01:36:15 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-28 01:36:16 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-28 01:36:16 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-28 01:36:16 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-28 01:36:16 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-28 01:36:16 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-28 01:36:16 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-28 01:36:16 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-28 01:36:16 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-28 01:36:16 (4259) [INFO] 
* 2023-10-28 01:36:16 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-28 01:36:16 (4229) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-28 01:36:26 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-28 01:36:26 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-28 01:36:26 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-28 01:36:26 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-28 01:36:26 (4242) [INFO] Trying other mirror.
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-28 01:36:26 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-28 01:36:26 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-28 01:36:26 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-28 01:36:26 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-28 01:36:26 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-28 01:36:26 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-28 01:36:26 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-28 01:36:26 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-28 01:36:26 (4242) [INFO]         or
* 2023-10-28 01:36:26 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-28 01:36:26 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-28 01:36:26 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-28 01:36:26 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-28 01:36:26 (4242) [INFO]         compromise:
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-28 01:36:26 (4242) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-28 01:36:26 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-28 01:36:26 (4259) [INFO] 
* 2023-10-28 01:36:26 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-28 01:36:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-28 01:36:26 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-28 01:36:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-28 01:36:27 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-28 01:36:27 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-28 01:36:27 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-28 01:36:27 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-28 01:36:27 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-28 01:36:27 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-28 01:36:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-28 01:36:27 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-28 01:36:27 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-28 01:36:31 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-28 01:36:31 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-28 01:36:31 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-28 01:36:31 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-28 01:36:31 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-28 01:36:31 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-28 01:36:31 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/K5GrOfVHIF/ea_profile.json
* 2023-10-28 01:36:34 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/K5GrOfVHIF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-28 01:36:34 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-29 01:34:31 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-29 01:34:31 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-10-29 01:34:32 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-29 01:34:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-29 01:34:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-29 01:34:32 (4229) [INFO] 
* 2023-10-29 01:34:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-29 01:34:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-29 01:34:32 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-29 01:34:32 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-29 01:34:32 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-29 01:34:32 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-29 01:34:32 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-29 01:34:32 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-29 01:34:32 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-29 01:34:32 (4259) [INFO] 
* 2023-10-29 01:34:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-29 01:34:32 (4229) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-29 01:34:41 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-29 01:34:41 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-29 01:34:41 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-29 01:34:41 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-29 01:34:41 (4242) [INFO] Trying other mirror.
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-29 01:34:41 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-29 01:34:41 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-29 01:34:41 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-29 01:34:41 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-29 01:34:41 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-29 01:34:41 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-29 01:34:41 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-29 01:34:41 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-29 01:34:41 (4242) [INFO]         or
* 2023-10-29 01:34:41 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-29 01:34:41 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-29 01:34:41 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-29 01:34:41 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-29 01:34:41 (4242) [INFO]         compromise:
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-29 01:34:41 (4242) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-29 01:34:41 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-29 01:34:41 (4259) [INFO] 
* 2023-10-29 01:34:41 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-29 01:34:41 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-29 01:34:41 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-29 01:34:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-29 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-29 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-29 01:34:42 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-29 01:34:42 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-29 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-29 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-29 01:34:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-29 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-29 01:34:42 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-29 01:34:45 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-29 01:34:45 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-29 01:34:45 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-29 01:34:45 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-29 01:34:45 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-29 01:34:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-29 01:34:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/a9xnoKkYvn/ea_profile.json
* 2023-10-29 01:34:49 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/a9xnoKkYvn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-29 01:34:49 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-30 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-30 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-10-30 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-30 01:33:44 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-30 01:33:44 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-30 01:33:44 (4229) [INFO] 
* 2023-10-30 01:33:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-30 01:33:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-30 01:33:44 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-30 01:33:44 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-30 01:33:44 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-30 01:33:44 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-30 01:33:44 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-30 01:33:44 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-30 01:33:44 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-30 01:33:44 (4259) [INFO] 
* 2023-10-30 01:33:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-30 01:33:44 (4229) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-30 01:33:59 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-30 01:33:59 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-30 01:33:59 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-30 01:33:59 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-30 01:33:59 (4242) [INFO] Trying other mirror.
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-30 01:33:59 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-30 01:33:59 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-30 01:33:59 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-30 01:33:59 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-30 01:33:59 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-30 01:33:59 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-30 01:33:59 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-30 01:33:59 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-30 01:33:59 (4242) [INFO]         or
* 2023-10-30 01:33:59 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-30 01:33:59 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-30 01:33:59 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-30 01:33:59 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-30 01:33:59 (4242) [INFO]         compromise:
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-30 01:33:59 (4242) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-30 01:33:59 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-30 01:33:59 (4259) [INFO] 
* 2023-10-30 01:33:59 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-30 01:33:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-30 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-30 01:34:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-30 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-30 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-30 01:34:01 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-30 01:34:01 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-30 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-30 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-30 01:34:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-30 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-30 01:34:01 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-30 01:34:07 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-30 01:34:07 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-30 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-30 01:34:07 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-30 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-30 01:34:07 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-30 01:34:07 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0enCwjj9pD/ea_profile.json
* 2023-10-30 01:34:13 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0enCwjj9pD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-30 01:34:13 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-31 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-10-31 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-10-31 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-10-31 01:33:56 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-31 01:33:56 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-31 01:33:56 (4229) [INFO] 
* 2023-10-31 01:33:56 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-31 01:33:56 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-10-31 01:33:56 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-10-31 01:33:56 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-10-31 01:33:56 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-10-31 01:33:56 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-10-31 01:33:56 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-10-31 01:33:56 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-10-31 01:33:56 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-10-31 01:33:56 (4259) [INFO] 
* 2023-10-31 01:33:56 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-31 01:33:56 (4229) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-10-31 01:34:07 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-10-31 01:34:07 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-10-31 01:34:07 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-10-31 01:34:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-31 01:34:07 (4242) [INFO] Trying other mirror.
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-10-31 01:34:07 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-31 01:34:07 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-31 01:34:07 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-31 01:34:07 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-31 01:34:07 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-31 01:34:07 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-31 01:34:07 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-31 01:34:07 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-10-31 01:34:07 (4242) [INFO]         or
* 2023-10-31 01:34:07 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-31 01:34:07 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-31 01:34:07 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-31 01:34:07 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-31 01:34:07 (4242) [INFO]         compromise:
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-10-31 01:34:07 (4242) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-10-31 01:34:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-31 01:34:07 (4259) [INFO] 
* 2023-10-31 01:34:07 (4242) [INFO] Is this ok [y/N]: 
* 2023-10-31 01:34:07 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-31 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-31 01:34:09 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-10-31 01:34:09 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-10-31 01:34:09 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-10-31 01:34:09 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-10-31 01:34:09 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-10-31 01:34:09 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-10-31 01:34:09 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-10-31 01:34:09 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-10-31 01:34:09 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-10-31 01:34:09 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-10-31 01:34:15 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-31 01:34:15 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-10-31 01:34:15 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-31 01:34:15 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-10-31 01:34:15 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-10-31 01:34:15 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-31 01:34:15 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dRvwiKVUj_/ea_profile.json
* 2023-10-31 01:34:20 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dRvwiKVUj_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-31 01:34:20 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-01 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-01 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-01 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-01 01:33:52 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-01 01:33:52 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-01 01:33:52 (4229) [INFO] 
* 2023-11-01 01:33:52 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-01 01:33:53 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-01 01:33:53 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-01 01:33:53 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-01 01:33:53 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-01 01:33:53 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-01 01:33:53 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-01 01:33:53 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-01 01:33:53 (4242) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2023-11-01 01:33:53 (4259) [INFO] 
* 2023-11-01 01:33:53 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-01 01:33:53 (4229) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]  One of the configured repositories failed (Unknown),
* 2023-11-01 01:34:01 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-01 01:34:01 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-01 01:34:01 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-01 01:34:01 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-01 01:34:01 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-01 01:34:01 (4242) [INFO]             yum --disablerepo=<repoid> ...
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-01 01:34:01 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-01 01:34:01 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]             yum-config-manager --disable <repoid>
* 2023-11-01 01:34:01 (4242) [INFO]         or
* 2023-11-01 01:34:01 (4242) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-01 01:34:01 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-01 01:34:01 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-01 01:34:01 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-01 01:34:01 (4242) [INFO]         compromise:
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-11-01 01:34:01 (4242) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2023-11-01 01:34:01 (4242) [INFO]     * free   0 
* 2023-11-01 01:34:01 (4242) [INFO]     * needed 100 k
* 2023-11-01 01:34:01 (4259) [INFO] 
* 2023-11-01 01:34:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-01 01:34:01 (1773) [INFO] Checking /scripts/sysup
* 2023-11-01 01:34:01 (4228) [INFO] Running: /scripts/sysup
* 2023-11-01 01:34:01 (4229) [INFO] 
* 2023-11-01 01:34:01 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-11-01 01:34:02 (4242) [INFO]   All Needed Packages are already installed.
* 2023-11-01 01:34:02 (4259) [INFO] 
* 2023-11-01 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-01 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-01 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-01 01:34:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-01 01:34:04 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-01 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-01 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-01 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-01 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-01 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-01 01:34:07 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-01 01:34:07 (1619) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2023-11-01 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-01 01:34:07 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-01 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-01 01:34:07 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-01 01:34:07 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lDmskRPyeo/ea_profile.json
* 2023-11-01 01:34:08 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lDmskRPyeo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-01 01:34:08 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-02 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-02 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-02 01:33:54 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-02 01:33:54 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-02 01:33:54 (4229) [INFO] 
* 2023-11-02 01:33:54 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-02 01:33:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-02 01:33:54 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-02 01:33:54 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-02 01:33:54 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-02 01:33:54 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-02 01:33:54 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-02 01:33:54 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-02 01:33:54 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-02 01:33:54 (4259) [INFO] 
* 2023-11-02 01:33:54 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-02 01:33:54 (4229) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-02 01:34:06 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-02 01:34:06 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-02 01:34:06 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-02 01:34:06 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-02 01:34:06 (4242) [INFO] Trying other mirror.
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-02 01:34:06 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-02 01:34:06 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-02 01:34:06 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-02 01:34:06 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-02 01:34:06 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-02 01:34:06 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-02 01:34:06 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-02 01:34:06 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-02 01:34:06 (4242) [INFO]         or
* 2023-11-02 01:34:06 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-02 01:34:06 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-02 01:34:06 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-02 01:34:06 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-02 01:34:06 (4242) [INFO]         compromise:
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-02 01:34:06 (4242) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-02 01:34:06 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-02 01:34:06 (4259) [INFO] 
* 2023-11-02 01:34:06 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-02 01:34:06 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-02 01:34:06 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-02 01:34:07 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-02 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-02 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-02 01:34:07 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-02 01:34:07 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-02 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-02 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-02 01:34:07 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-02 01:34:07 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-02 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-02 01:34:11 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-02 01:34:11 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-02 01:34:11 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-02 01:34:11 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-02 01:34:11 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-02 01:34:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-02 01:34:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z0HHuQklul/ea_profile.json
* 2023-11-02 01:34:15 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z0HHuQklul/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-02 01:34:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-03 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-03 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-03 01:33:55 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-03 01:33:55 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-03 01:33:55 (4229) [INFO] 
* 2023-11-03 01:33:55 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-03 01:33:55 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-03 01:33:55 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-03 01:33:55 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-03 01:33:55 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-03 01:33:55 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-03 01:33:55 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-03 01:33:55 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-03 01:33:55 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-03 01:33:55 (4259) [INFO] 
* 2023-11-03 01:33:55 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-03 01:33:55 (4229) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-03 01:34:07 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-03 01:34:07 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-03 01:34:07 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-03 01:34:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-03 01:34:07 (4242) [INFO] Trying other mirror.
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-03 01:34:07 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-03 01:34:07 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-03 01:34:07 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-03 01:34:07 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-03 01:34:07 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-03 01:34:07 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-03 01:34:07 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-03 01:34:07 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-03 01:34:07 (4242) [INFO]         or
* 2023-11-03 01:34:07 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-03 01:34:07 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-03 01:34:07 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-03 01:34:07 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-03 01:34:07 (4242) [INFO]         compromise:
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-03 01:34:07 (4242) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-03 01:34:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-03 01:34:07 (4259) [INFO] 
* 2023-11-03 01:34:07 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-03 01:34:07 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-03 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-03 01:34:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-03 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-03 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-03 01:34:08 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-03 01:34:08 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-03 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-03 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-03 01:34:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-03 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-03 01:34:08 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-03 01:34:13 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-03 01:34:13 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-03 01:34:13 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-03 01:34:13 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-03 01:34:13 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-03 01:34:13 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-03 01:34:13 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6iBK5Ibrul/ea_profile.json
* 2023-11-03 01:34:17 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6iBK5Ibrul/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-03 01:34:17 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-04 01:34:43 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-04 01:34:44 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-04 01:34:44 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-04 01:34:44 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-04 01:34:44 (4229) [INFO] 
* 2023-11-04 01:34:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-04 01:34:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-04 01:34:45 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-04 01:34:45 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-04 01:34:45 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-04 01:34:45 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-04 01:34:45 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-04 01:34:45 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-04 01:34:45 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-04 01:34:45 (4259) [INFO] 
* 2023-11-04 01:34:45 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-04 01:34:45 (4229) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-04 01:34:58 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-04 01:34:58 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-04 01:34:58 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-04 01:34:58 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-04 01:34:58 (4242) [INFO] Trying other mirror.
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-04 01:34:58 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-04 01:34:58 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-04 01:34:58 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-04 01:34:58 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-04 01:34:58 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-04 01:34:58 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-04 01:34:58 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-04 01:34:58 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-04 01:34:58 (4242) [INFO]         or
* 2023-11-04 01:34:58 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-04 01:34:58 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-04 01:34:58 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-04 01:34:58 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-04 01:34:58 (4242) [INFO]         compromise:
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-04 01:34:58 (4242) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-04 01:34:58 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-04 01:34:58 (4259) [INFO] 
* 2023-11-04 01:34:58 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-04 01:34:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-04 01:34:58 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-04 01:34:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-04 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-04 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-04 01:34:59 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-04 01:34:59 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-04 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-04 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-04 01:34:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-04 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-04 01:34:59 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-04 01:35:02 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-04 01:35:02 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-04 01:35:02 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-04 01:35:02 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-04 01:35:02 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-04 01:35:03 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-04 01:35:03 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KpxD3ZcP5O/ea_profile.json
* 2023-11-04 01:35:08 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KpxD3ZcP5O/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-04 01:35:08 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-05 01:34:55 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-05 01:34:56 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-05 01:34:56 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-05 01:34:56 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-05 01:34:56 (4229) [INFO] 
* 2023-11-05 01:34:56 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-05 01:34:56 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-05 01:34:56 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-05 01:34:56 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-05 01:34:56 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-05 01:34:56 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-05 01:34:56 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-05 01:34:56 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-05 01:34:56 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-05 01:34:56 (4259) [INFO] 
* 2023-11-05 01:34:56 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-05 01:34:56 (4229) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-05 01:35:08 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-05 01:35:08 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-05 01:35:08 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-05 01:35:08 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-05 01:35:08 (4242) [INFO] Trying other mirror.
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-05 01:35:08 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-05 01:35:08 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-05 01:35:08 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-05 01:35:08 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-05 01:35:08 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-05 01:35:08 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-05 01:35:08 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-05 01:35:08 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-05 01:35:08 (4242) [INFO]         or
* 2023-11-05 01:35:08 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-05 01:35:08 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-05 01:35:08 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-05 01:35:08 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-05 01:35:08 (4242) [INFO]         compromise:
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-05 01:35:08 (4242) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-05 01:35:08 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-05 01:35:08 (4259) [INFO] 
* 2023-11-05 01:35:08 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-05 01:35:08 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-05 01:35:08 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-05 01:35:09 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-05 01:35:09 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-05 01:35:09 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-05 01:35:09 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-05 01:35:09 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-05 01:35:09 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-05 01:35:09 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-05 01:35:09 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-05 01:35:09 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-05 01:35:09 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-05 01:35:13 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-05 01:35:13 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-05 01:35:13 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-05 01:35:13 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-05 01:35:13 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-05 01:35:13 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-05 01:35:13 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YemPQPR8ug/ea_profile.json
* 2023-11-05 01:35:16 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YemPQPR8ug/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-05 01:35:16 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-06 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-06 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-06 01:33:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-06 01:33:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-06 01:33:49 (4229) [INFO] 
* 2023-11-06 01:33:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-06 01:33:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-06 01:33:50 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-06 01:33:50 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-06 01:33:50 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-06 01:33:50 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-06 01:33:50 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-06 01:33:50 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-06 01:33:50 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-06 01:33:50 (4259) [INFO] 
* 2023-11-06 01:33:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-06 01:33:50 (4229) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-06 01:34:00 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-06 01:34:00 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-06 01:34:00 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-06 01:34:00 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-06 01:34:00 (4242) [INFO] Trying other mirror.
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-06 01:34:00 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-06 01:34:00 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-06 01:34:00 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-06 01:34:00 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-06 01:34:00 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-06 01:34:00 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-06 01:34:00 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-06 01:34:00 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-06 01:34:00 (4242) [INFO]         or
* 2023-11-06 01:34:00 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-06 01:34:00 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-06 01:34:00 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-06 01:34:00 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-06 01:34:00 (4242) [INFO]         compromise:
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-06 01:34:00 (4242) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-06 01:34:00 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-06 01:34:00 (4259) [INFO] 
* 2023-11-06 01:34:00 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-06 01:34:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-06 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-06 01:34:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-06 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-06 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-06 01:34:01 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-06 01:34:01 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-06 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-06 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-06 01:34:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-06 01:34:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-06 01:34:01 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-06 01:34:04 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-06 01:34:04 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-06 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-06 01:34:04 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-06 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-06 01:34:05 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-06 01:34:05 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TFJTMHIsUh/ea_profile.json
* 2023-11-06 01:34:11 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TFJTMHIsUh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-06 01:34:11 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-07 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-07 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-07 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-07 01:33:43 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-07 01:33:43 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-07 01:33:43 (4229) [INFO] 
* 2023-11-07 01:33:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-07 01:33:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-07 01:33:44 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-07 01:33:44 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-07 01:33:44 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-07 01:33:44 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-07 01:33:44 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-07 01:33:44 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-07 01:33:44 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-07 01:33:44 (4259) [INFO] 
* 2023-11-07 01:33:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-07 01:33:44 (4229) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-07 01:33:57 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-07 01:33:57 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-07 01:33:57 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-07 01:33:57 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-07 01:33:57 (4242) [INFO] Trying other mirror.
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-07 01:33:57 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-07 01:33:57 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-07 01:33:57 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-07 01:33:57 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-07 01:33:57 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-07 01:33:57 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-07 01:33:57 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-07 01:33:57 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-07 01:33:57 (4242) [INFO]         or
* 2023-11-07 01:33:57 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-07 01:33:57 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-07 01:33:57 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-07 01:33:57 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-07 01:33:57 (4242) [INFO]         compromise:
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-07 01:33:57 (4242) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-07 01:33:57 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-07 01:33:57 (4259) [INFO] 
* 2023-11-07 01:33:57 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-07 01:33:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-07 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-07 01:33:58 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-07 01:33:58 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-07 01:33:58 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-07 01:33:58 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-07 01:33:58 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-07 01:33:58 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-07 01:33:58 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-07 01:33:58 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-07 01:33:58 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-07 01:33:58 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-07 01:34:04 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-07 01:34:04 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-07 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-07 01:34:04 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-07 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-07 01:34:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-07 01:34:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9nVsxXHMG2/ea_profile.json
* 2023-11-07 01:34:13 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9nVsxXHMG2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-07 01:34:13 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-08 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-08 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-08 01:34:01 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-08 01:34:01 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-08 01:34:01 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-08 01:34:01 (4229) [INFO] 
* 2023-11-08 01:34:01 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-08 01:34:01 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-08 01:34:01 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-08 01:34:01 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-08 01:34:01 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-08 01:34:01 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-08 01:34:01 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-08 01:34:01 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-08 01:34:01 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-08 01:34:01 (4259) [INFO] 
* 2023-11-08 01:34:01 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-08 01:34:01 (4229) [INFO] 
* 2023-11-08 01:34:40 (4242) [INFO] https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-11-08 01:34:40 (4242) [INFO] Trying other mirror.
* 2023-11-08 01:34:56 (4242) [INFO] https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to cdn.centos.no:443; Operation now in progress"
* 2023-11-08 01:34:56 (4242) [INFO] Trying other mirror.
* 2023-11-08 01:34:57 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-08 01:34:57 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-08 01:34:57 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-08 01:34:57 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-08 01:34:57 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-08 01:34:57 (4242) [INFO] Trying other mirror.
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-08 01:34:57 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-08 01:34:57 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-08 01:34:57 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-08 01:34:57 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-08 01:34:57 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-08 01:34:57 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-08 01:34:57 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-08 01:34:57 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-08 01:34:57 (4242) [INFO]         or
* 2023-11-08 01:34:57 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-08 01:34:57 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-08 01:34:57 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-08 01:34:57 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-08 01:34:57 (4242) [INFO]         compromise:
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-08 01:34:57 (4242) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-08 01:34:57 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-08 01:34:57 (4259) [INFO] 
* 2023-11-08 01:34:57 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-08 01:34:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-08 01:34:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-08 01:34:58 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-08 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-08 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-08 01:34:59 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-08 01:34:59 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-08 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-08 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-08 01:34:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-08 01:34:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-08 01:34:59 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-08 01:35:29 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-08 01:35:29 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-08 01:35:29 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-08 01:35:29 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-08 01:35:29 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-08 01:35:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-08 01:35:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7i2Vd9wJWu/ea_profile.json
* 2023-11-08 01:35:34 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7i2Vd9wJWu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-08 01:35:34 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-09 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-09 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-09 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-09 01:34:26 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-09 01:34:26 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-09 01:34:26 (4229) [INFO] 
* 2023-11-09 01:34:27 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-09 01:34:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-09 01:34:27 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-09 01:34:27 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-09 01:34:27 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-09 01:34:27 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-09 01:34:27 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-09 01:34:27 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-09 01:34:27 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-09 01:34:27 (4259) [INFO] 
* 2023-11-09 01:34:27 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-09 01:34:27 (4229) [INFO] 
* 2023-11-09 01:35:08 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2023-11-09 01:35:08 (4242) [INFO] Trying other mirror.
* 2023-11-09 01:35:24 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-09 01:35:24 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-09 01:35:24 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-09 01:35:24 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-09 01:35:24 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-09 01:35:24 (4242) [INFO] Trying other mirror.
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-09 01:35:24 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-09 01:35:24 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-09 01:35:24 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-09 01:35:24 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-09 01:35:24 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-09 01:35:24 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-09 01:35:24 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-09 01:35:24 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-09 01:35:24 (4242) [INFO]         or
* 2023-11-09 01:35:24 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-09 01:35:24 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-09 01:35:24 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-09 01:35:24 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-09 01:35:24 (4242) [INFO]         compromise:
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-09 01:35:24 (4242) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-09 01:35:24 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-09 01:35:24 (4259) [INFO] 
* 2023-11-09 01:35:24 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-09 01:35:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-09 01:35:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-09 01:35:25 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-09 01:35:25 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-09 01:35:25 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-09 01:35:25 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-09 01:35:25 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-09 01:35:25 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-09 01:35:25 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-09 01:35:25 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-09 01:35:25 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-09 01:35:25 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-09 01:36:09 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-09 01:36:09 (1619) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress"
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-09 01:36:09 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-09 01:36:09 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-09 01:36:09 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-09 01:36:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-09 01:36:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iMlYj7a1r1/ea_profile.json
* 2023-11-09 01:36:26 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iMlYj7a1r1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-09 01:36:26 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-10 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-10 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-10 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-10 01:33:57 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-10 01:33:57 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-10 01:33:57 (4229) [INFO] 
* 2023-11-10 01:33:58 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-10 01:33:58 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-10 01:33:58 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-10 01:33:58 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-10 01:33:58 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-10 01:33:58 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-10 01:33:58 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-10 01:33:58 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-10 01:33:58 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-10 01:33:58 (4259) [INFO] 
* 2023-11-10 01:33:58 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-10 01:33:58 (4229) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-10 01:34:40 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-10 01:34:40 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-10 01:34:40 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-10 01:34:40 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-10 01:34:40 (4242) [INFO] Trying other mirror.
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-10 01:34:40 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-10 01:34:40 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-10 01:34:40 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-10 01:34:40 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-10 01:34:40 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-10 01:34:40 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-10 01:34:40 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-10 01:34:40 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-10 01:34:40 (4242) [INFO]         or
* 2023-11-10 01:34:40 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-10 01:34:40 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-10 01:34:40 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-10 01:34:40 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-10 01:34:40 (4242) [INFO]         compromise:
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-10 01:34:40 (4242) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-10 01:34:40 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-10 01:34:40 (4259) [INFO] 
* 2023-11-10 01:34:40 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-10 01:34:40 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-10 01:34:40 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-10 01:34:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-10 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-10 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-10 01:34:42 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-10 01:34:42 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-10 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-10 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-10 01:34:42 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-10 01:34:42 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-10 01:34:42 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-10 01:34:47 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-10 01:34:47 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-10 01:34:47 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-10 01:34:47 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-10 01:34:47 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-10 01:34:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-10 01:34:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s5wL8mfLRT/ea_profile.json
* 2023-11-10 01:34:50 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s5wL8mfLRT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-10 01:34:50 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-11 01:35:20 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-11 01:35:20 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-11 01:35:20 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-11 01:35:20 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-11 01:35:20 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-11 01:35:20 (4229) [INFO] 
* 2023-11-11 01:35:21 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-11 01:35:21 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-11 01:35:21 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-11 01:35:21 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-11 01:35:21 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-11 01:35:21 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-11 01:35:21 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-11 01:35:21 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-11 01:35:21 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-11 01:35:21 (4259) [INFO] 
* 2023-11-11 01:35:21 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-11 01:35:21 (4229) [INFO] 
* 2023-11-11 01:36:00 (4242) [INFO] https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to repo.mongodb.org:443; Operation now in progress"
* 2023-11-11 01:36:00 (4242) [INFO] Trying other mirror.
* 2023-11-11 01:36:30 (4242) [INFO] https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to repo.mongodb.org:443; Operation now in progress"
* 2023-11-11 01:36:30 (4242) [INFO] Trying other mirror.
* 2023-11-11 01:37:00 (4242) [INFO] https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to repo.mongodb.org:443; Operation now in progress"
* 2023-11-11 01:37:00 (4242) [INFO] Trying other mirror.
* 2023-11-11 01:37:03 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-11 01:37:03 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-11 01:37:03 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-11 01:37:03 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-11 01:37:03 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-11 01:37:03 (4242) [INFO] Trying other mirror.
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-11 01:37:03 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-11 01:37:03 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-11 01:37:03 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-11 01:37:03 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-11 01:37:03 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-11 01:37:03 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-11 01:37:03 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-11 01:37:03 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-11 01:37:03 (4242) [INFO]         or
* 2023-11-11 01:37:03 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-11 01:37:03 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-11 01:37:03 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-11 01:37:03 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-11 01:37:03 (4242) [INFO]         compromise:
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-11 01:37:03 (4242) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-11 01:37:03 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-11 01:37:03 (4259) [INFO] 
* 2023-11-11 01:37:03 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-11 01:37:03 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-11 01:37:03 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-11 01:37:05 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-11 01:37:05 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-11 01:37:05 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-11 01:37:05 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-11 01:37:05 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-11 01:37:05 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-11 01:37:05 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-11 01:37:05 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-11 01:37:05 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-11 01:37:05 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-11 01:37:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-11 01:37:10 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-11 01:37:10 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-11 01:37:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-11 01:37:10 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-11 01:37:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-11 01:37:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o2c75KUIl3/ea_profile.json
* 2023-11-11 01:37:14 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o2c75KUIl3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-11 01:37:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-12 01:35:15 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-12 01:35:15 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-12 01:35:15 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-12 01:35:15 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-12 01:35:15 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-12 01:35:15 (4229) [INFO] 
* 2023-11-12 01:35:15 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-12 01:35:16 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-12 01:35:16 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-12 01:35:16 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-12 01:35:16 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-12 01:35:16 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-12 01:35:16 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-12 01:35:16 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-12 01:35:16 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-12 01:35:16 (4259) [INFO] 
* 2023-11-12 01:35:16 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-12 01:35:16 (4229) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-12 01:35:26 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-12 01:35:26 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-12 01:35:26 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-12 01:35:26 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-12 01:35:26 (4242) [INFO] Trying other mirror.
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-12 01:35:26 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-12 01:35:26 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-12 01:35:26 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-12 01:35:26 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-12 01:35:26 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-12 01:35:26 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-12 01:35:26 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-12 01:35:26 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-12 01:35:26 (4242) [INFO]         or
* 2023-11-12 01:35:26 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-12 01:35:26 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-12 01:35:26 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-12 01:35:26 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-12 01:35:26 (4242) [INFO]         compromise:
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-12 01:35:26 (4242) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-12 01:35:26 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-12 01:35:26 (4259) [INFO] 
* 2023-11-12 01:35:26 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-12 01:35:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-12 01:35:26 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-12 01:35:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-12 01:35:27 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-12 01:35:27 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-12 01:35:27 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-12 01:35:27 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-12 01:35:27 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-12 01:35:27 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-12 01:35:27 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-12 01:35:27 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-12 01:35:27 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-12 01:35:30 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-12 01:35:30 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-12 01:35:30 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-12 01:35:30 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-12 01:35:30 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-12 01:35:31 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-12 01:35:32 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wmjIcSUyAw/ea_profile.json
* 2023-11-12 01:35:35 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wmjIcSUyAw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-12 01:35:35 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-13 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-13 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-11-13 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-13 01:33:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-13 01:33:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-13 01:33:33 (4229) [INFO] 
* 2023-11-13 01:33:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-13 01:33:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-13 01:33:33 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-13 01:33:33 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-13 01:33:33 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-13 01:33:33 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-13 01:33:33 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-13 01:33:33 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-13 01:33:33 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-13 01:33:34 (4259) [INFO] 
* 2023-11-13 01:33:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-13 01:33:34 (4229) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-13 01:33:46 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-13 01:33:46 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-13 01:33:46 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-13 01:33:46 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-13 01:33:46 (4242) [INFO] Trying other mirror.
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-13 01:33:46 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-13 01:33:46 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-13 01:33:46 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-13 01:33:46 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-13 01:33:46 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-13 01:33:46 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-13 01:33:46 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-13 01:33:46 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-13 01:33:46 (4242) [INFO]         or
* 2023-11-13 01:33:46 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-13 01:33:46 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-13 01:33:46 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-13 01:33:46 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-13 01:33:46 (4242) [INFO]         compromise:
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-13 01:33:46 (4242) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-13 01:33:46 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-13 01:33:46 (4259) [INFO] 
* 2023-11-13 01:33:46 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-13 01:33:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-13 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-13 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-13 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-13 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-13 01:33:47 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-13 01:33:47 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-13 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-13 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-13 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-13 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-13 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-13 01:33:51 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-13 01:33:51 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-13 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-13 01:33:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-13 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-13 01:33:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-13 01:33:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XoR8HLfnUJ/ea_profile.json
* 2023-11-13 01:33:58 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XoR8HLfnUJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-13 01:33:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-14 01:34:18 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-14 01:34:19 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-14 01:34:19 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-14 01:34:19 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-14 01:34:19 (4229) [INFO] 
* 2023-11-14 01:34:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-14 01:34:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-14 01:34:19 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-14 01:34:19 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-14 01:34:19 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-14 01:34:19 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-14 01:34:19 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-14 01:34:19 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-14 01:34:19 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-14 01:34:19 (4259) [INFO] 
* 2023-11-14 01:34:19 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-14 01:34:19 (4229) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-14 01:34:32 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-14 01:34:32 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-14 01:34:32 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-14 01:34:32 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-14 01:34:32 (4242) [INFO] Trying other mirror.
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-14 01:34:32 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-14 01:34:32 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-14 01:34:32 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-14 01:34:32 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-14 01:34:32 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-14 01:34:32 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-14 01:34:32 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-14 01:34:32 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-14 01:34:32 (4242) [INFO]         or
* 2023-11-14 01:34:32 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-14 01:34:32 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-14 01:34:32 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-14 01:34:32 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-14 01:34:32 (4242) [INFO]         compromise:
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-14 01:34:32 (4242) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-14 01:34:32 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-14 01:34:32 (4259) [INFO] 
* 2023-11-14 01:34:32 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-14 01:34:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-14 01:34:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-14 01:34:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-14 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-14 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-14 01:34:33 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-14 01:34:33 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-14 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-14 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-14 01:34:33 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-14 01:34:33 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-14 01:34:33 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-14 01:34:37 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-14 01:34:37 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-14 01:34:37 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-14 01:34:37 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-14 01:34:37 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-14 01:34:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-14 01:34:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qFbH1QYzXD/ea_profile.json
* 2023-11-14 01:34:41 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qFbH1QYzXD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-14 01:34:41 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-15 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-15 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-15 01:33:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-15 01:33:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-15 01:33:33 (4229) [INFO] 
* 2023-11-15 01:33:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-15 01:33:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-15 01:33:34 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-15 01:33:34 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-15 01:33:34 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-15 01:33:34 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-15 01:33:34 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-15 01:33:34 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-15 01:33:34 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-15 01:33:34 (4259) [INFO] 
* 2023-11-15 01:33:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-15 01:33:34 (4229) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-15 01:33:46 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-15 01:33:46 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-15 01:33:46 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-15 01:33:46 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-15 01:33:46 (4242) [INFO] Trying other mirror.
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-15 01:33:46 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-15 01:33:46 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-15 01:33:46 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-15 01:33:46 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-15 01:33:46 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-15 01:33:46 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-15 01:33:46 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-15 01:33:46 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-15 01:33:46 (4242) [INFO]         or
* 2023-11-15 01:33:46 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-15 01:33:46 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-15 01:33:46 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-15 01:33:46 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-15 01:33:46 (4242) [INFO]         compromise:
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-15 01:33:46 (4242) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-15 01:33:46 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-15 01:33:46 (4259) [INFO] 
* 2023-11-15 01:33:46 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-15 01:33:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-15 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-15 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-15 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-15 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-15 01:33:47 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-15 01:33:47 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-15 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-15 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-15 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-15 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-15 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-15 01:33:53 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-15 01:33:53 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-15 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-15 01:33:53 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-15 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-15 01:33:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-15 01:33:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WnserwMtMm/ea_profile.json
* 2023-11-15 01:33:58 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WnserwMtMm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-15 01:33:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-16 01:34:14 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-16 01:34:15 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-16 01:34:15 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-16 01:34:15 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-16 01:34:15 (4229) [INFO] 
* 2023-11-16 01:34:15 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-16 01:34:15 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-16 01:34:15 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-16 01:34:15 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-16 01:34:15 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-16 01:34:15 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-16 01:34:15 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-16 01:34:15 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-16 01:34:15 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-16 01:34:15 (4259) [INFO] 
* 2023-11-16 01:34:15 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-16 01:34:15 (4229) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-16 01:34:34 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-16 01:34:34 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-16 01:34:34 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-16 01:34:34 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-16 01:34:34 (4242) [INFO] Trying other mirror.
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-16 01:34:34 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-16 01:34:34 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-16 01:34:34 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-16 01:34:34 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-16 01:34:34 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-16 01:34:34 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-16 01:34:34 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-16 01:34:34 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-16 01:34:34 (4242) [INFO]         or
* 2023-11-16 01:34:34 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-16 01:34:34 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-16 01:34:34 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-16 01:34:34 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-16 01:34:34 (4242) [INFO]         compromise:
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-16 01:34:34 (4242) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-16 01:34:34 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-16 01:34:34 (4259) [INFO] 
* 2023-11-16 01:34:34 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-16 01:34:34 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-16 01:34:34 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-16 01:34:36 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-16 01:34:36 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-16 01:34:36 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-16 01:34:36 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-16 01:34:36 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-16 01:34:36 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-16 01:34:36 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-16 01:34:36 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-16 01:34:36 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-16 01:34:36 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-16 01:34:42 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-16 01:34:42 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-16 01:34:42 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-16 01:34:42 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-16 01:34:42 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-16 01:34:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-16 01:34:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MDAYaq9Tjj/ea_profile.json
* 2023-11-16 01:34:48 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MDAYaq9Tjj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-16 01:34:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-17 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-17 01:33:33 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-17 01:33:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-17 01:33:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-17 01:33:33 (4229) [INFO] 
* 2023-11-17 01:33:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-17 01:33:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-17 01:33:33 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-17 01:33:33 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-17 01:33:33 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-17 01:33:33 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-17 01:33:33 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-17 01:33:33 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-17 01:33:33 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-17 01:33:34 (4259) [INFO] 
* 2023-11-17 01:33:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-17 01:33:34 (4229) [INFO] 
* 2023-11-17 01:34:11 (4242) [INFO] https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-11-17 01:34:11 (4242) [INFO] Trying other mirror.
* 2023-11-17 01:34:12 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-17 01:34:12 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-17 01:34:12 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-17 01:34:12 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-17 01:34:12 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-17 01:34:12 (4242) [INFO] Trying other mirror.
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-17 01:34:12 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-17 01:34:12 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-17 01:34:12 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-17 01:34:12 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-17 01:34:12 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-17 01:34:12 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-17 01:34:12 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-17 01:34:12 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-17 01:34:12 (4242) [INFO]         or
* 2023-11-17 01:34:12 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-17 01:34:12 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-17 01:34:12 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-17 01:34:12 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-17 01:34:12 (4242) [INFO]         compromise:
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-17 01:34:12 (4242) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-17 01:34:12 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-17 01:34:12 (4259) [INFO] 
* 2023-11-17 01:34:12 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-17 01:34:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-17 01:34:12 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-17 01:34:13 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-17 01:34:13 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-17 01:34:13 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-17 01:34:13 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-17 01:34:13 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-17 01:34:13 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-17 01:34:13 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-17 01:34:13 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-17 01:34:13 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-17 01:34:13 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-17 01:34:17 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-17 01:34:17 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-17 01:34:17 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-17 01:34:17 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-17 01:34:17 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-17 01:34:17 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-17 01:34:17 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9Sg60BBCI9/ea_profile.json
* 2023-11-17 01:34:22 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9Sg60BBCI9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-17 01:34:22 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-18 01:34:39 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-18 01:34:40 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-18 01:34:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-18 01:34:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-18 01:34:40 (4229) [INFO] 
* 2023-11-18 01:34:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-18 01:34:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-18 01:34:40 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-18 01:34:40 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-18 01:34:40 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-18 01:34:40 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-18 01:34:40 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-18 01:34:40 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-18 01:34:40 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-18 01:34:40 (4259) [INFO] 
* 2023-11-18 01:34:40 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-18 01:34:40 (4229) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-18 01:34:50 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-18 01:34:50 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-18 01:34:50 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-18 01:34:50 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-18 01:34:50 (4242) [INFO] Trying other mirror.
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-18 01:34:50 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-18 01:34:50 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-18 01:34:50 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-18 01:34:50 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-18 01:34:50 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-18 01:34:50 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-18 01:34:50 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-18 01:34:50 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-18 01:34:50 (4242) [INFO]         or
* 2023-11-18 01:34:50 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-18 01:34:50 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-18 01:34:50 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-18 01:34:50 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-18 01:34:50 (4242) [INFO]         compromise:
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-18 01:34:50 (4242) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-18 01:34:50 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-18 01:34:50 (4259) [INFO] 
* 2023-11-18 01:34:50 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-18 01:34:50 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-18 01:34:50 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-18 01:34:51 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-18 01:34:51 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-18 01:34:51 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-18 01:34:51 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-18 01:34:51 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-18 01:34:51 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-18 01:34:51 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-18 01:34:51 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-18 01:34:51 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-18 01:34:51 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-18 01:34:54 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-18 01:34:54 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-18 01:34:54 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-18 01:34:54 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-18 01:34:54 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-18 01:34:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-18 01:34:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/w8d9GeTq5Q/ea_profile.json
* 2023-11-18 01:35:00 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/w8d9GeTq5Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-18 01:35:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-19 01:35:14 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-19 01:35:15 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-19 01:35:15 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-19 01:35:15 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-19 01:35:15 (4229) [INFO] 
* 2023-11-19 01:35:15 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-19 01:35:15 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-19 01:35:15 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-19 01:35:15 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-19 01:35:15 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-19 01:35:15 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-19 01:35:15 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-19 01:35:15 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-19 01:35:15 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-19 01:35:15 (4259) [INFO] 
* 2023-11-19 01:35:15 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-19 01:35:15 (4229) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-19 01:35:25 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-19 01:35:25 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-19 01:35:25 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-19 01:35:25 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-19 01:35:25 (4242) [INFO] Trying other mirror.
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-19 01:35:25 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-19 01:35:25 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-19 01:35:25 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-19 01:35:25 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-19 01:35:25 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-19 01:35:25 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-19 01:35:25 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-19 01:35:25 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-19 01:35:25 (4242) [INFO]         or
* 2023-11-19 01:35:25 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-19 01:35:25 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-19 01:35:25 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-19 01:35:25 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-19 01:35:25 (4242) [INFO]         compromise:
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-19 01:35:25 (4242) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-19 01:35:25 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-19 01:35:25 (4259) [INFO] 
* 2023-11-19 01:35:25 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-19 01:35:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-19 01:35:25 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-19 01:35:26 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-19 01:35:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-19 01:35:26 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-19 01:35:26 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-19 01:35:26 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-19 01:35:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-19 01:35:26 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-19 01:35:26 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-19 01:35:26 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-19 01:35:26 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-19 01:35:29 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-19 01:35:29 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-19 01:35:29 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-19 01:35:29 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-19 01:35:29 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-19 01:35:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-19 01:35:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OzZZruVrAF/ea_profile.json
* 2023-11-19 01:35:32 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OzZZruVrAF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-19 01:35:32 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-20 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-20 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-20 01:33:42 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-20 01:33:42 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-20 01:33:42 (4229) [INFO] 
* 2023-11-20 01:33:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-20 01:33:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-20 01:33:43 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-20 01:33:43 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-20 01:33:43 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-20 01:33:43 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-20 01:33:43 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-20 01:33:43 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-20 01:33:43 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-20 01:33:43 (4259) [INFO] 
* 2023-11-20 01:33:43 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-20 01:33:43 (4229) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-20 01:33:52 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-20 01:33:52 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-20 01:33:52 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-20 01:33:52 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-20 01:33:52 (4242) [INFO] Trying other mirror.
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-20 01:33:52 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-20 01:33:52 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-20 01:33:52 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-20 01:33:52 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-20 01:33:52 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-20 01:33:52 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-20 01:33:52 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-20 01:33:52 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-20 01:33:52 (4242) [INFO]         or
* 2023-11-20 01:33:52 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-20 01:33:52 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-20 01:33:52 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-20 01:33:52 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-20 01:33:52 (4242) [INFO]         compromise:
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-20 01:33:52 (4242) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-20 01:33:52 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-20 01:33:52 (4259) [INFO] 
* 2023-11-20 01:33:52 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-20 01:33:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-20 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-20 01:33:53 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-20 01:33:53 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-20 01:33:53 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-20 01:33:53 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-20 01:33:53 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-20 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-20 01:33:56 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-20 01:33:56 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-20 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-20 01:33:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-20 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-20 01:33:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-20 01:33:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bJhI0xIniA/ea_profile.json
* 2023-11-20 01:33:59 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bJhI0xIniA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-20 01:33:59 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-21 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-21 01:33:49 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-21 01:33:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-21 01:33:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-21 01:33:49 (4229) [INFO] 
* 2023-11-21 01:33:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-21 01:33:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-21 01:33:49 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-21 01:33:49 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-21 01:33:49 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-21 01:33:49 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-21 01:33:49 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-21 01:33:49 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-21 01:33:49 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-21 01:33:49 (4259) [INFO] 
* 2023-11-21 01:33:49 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-21 01:33:49 (4229) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-21 01:34:03 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-21 01:34:03 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-21 01:34:03 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-21 01:34:03 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-21 01:34:03 (4242) [INFO] Trying other mirror.
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-21 01:34:03 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-21 01:34:03 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-21 01:34:03 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-21 01:34:03 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-21 01:34:03 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-21 01:34:03 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-21 01:34:03 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-21 01:34:03 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-21 01:34:03 (4242) [INFO]         or
* 2023-11-21 01:34:03 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-21 01:34:03 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-21 01:34:03 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-21 01:34:03 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-21 01:34:03 (4242) [INFO]         compromise:
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-21 01:34:03 (4242) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-21 01:34:03 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-21 01:34:03 (4259) [INFO] 
* 2023-11-21 01:34:03 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-21 01:34:03 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-21 01:34:03 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-21 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-21 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-21 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-21 01:34:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-21 01:34:04 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-21 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-21 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-21 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-21 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-21 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-21 01:34:11 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-21 01:34:11 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-21 01:34:11 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-21 01:34:11 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-21 01:34:11 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-21 01:34:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-21 01:34:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7VnuwjaaH2/ea_profile.json
* 2023-11-21 01:34:14 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7VnuwjaaH2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-21 01:34:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-22 01:33:35 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-22 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-22 01:33:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-22 01:33:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-22 01:33:36 (4229) [INFO] 
* 2023-11-22 01:33:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-22 01:33:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-22 01:33:36 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-22 01:33:36 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-22 01:33:36 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-22 01:33:36 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-22 01:33:36 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-22 01:33:36 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-22 01:33:36 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-22 01:33:36 (4259) [INFO] 
* 2023-11-22 01:33:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-22 01:33:36 (4229) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-22 01:33:45 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-22 01:33:45 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-22 01:33:45 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-22 01:33:45 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-22 01:33:45 (4242) [INFO] Trying other mirror.
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-22 01:33:45 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-22 01:33:45 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-22 01:33:45 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-22 01:33:45 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-22 01:33:45 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-22 01:33:45 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-22 01:33:45 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-22 01:33:45 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-22 01:33:45 (4242) [INFO]         or
* 2023-11-22 01:33:45 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-22 01:33:45 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-22 01:33:45 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-22 01:33:45 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-22 01:33:45 (4242) [INFO]         compromise:
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-22 01:33:45 (4242) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-22 01:33:45 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-22 01:33:45 (4259) [INFO] 
* 2023-11-22 01:33:45 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-22 01:33:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-22 01:33:45 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-22 01:33:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-22 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-22 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-22 01:33:48 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-22 01:33:48 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-22 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-22 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-22 01:33:48 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-22 01:33:48 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-22 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-22 01:33:52 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-22 01:33:52 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-22 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-22 01:33:52 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-22 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-22 01:33:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-22 01:33:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/md88BKBM6b/ea_profile.json
* 2023-11-22 01:33:57 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/md88BKBM6b/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-22 01:33:57 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-23 01:33:45 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-23 01:33:45 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-23 01:33:45 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-23 01:33:45 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-23 01:33:45 (4229) [INFO] 
* 2023-11-23 01:33:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-23 01:33:46 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-23 01:33:46 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-23 01:33:46 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-23 01:33:46 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-23 01:33:46 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-23 01:33:46 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-23 01:33:46 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-23 01:33:46 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-23 01:33:46 (4259) [INFO] 
* 2023-11-23 01:33:46 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-23 01:33:46 (4229) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-23 01:34:04 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-23 01:34:04 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-23 01:34:04 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-23 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-23 01:34:04 (4242) [INFO] Trying other mirror.
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-23 01:34:04 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-23 01:34:04 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-23 01:34:04 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-23 01:34:04 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-23 01:34:04 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-23 01:34:04 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-23 01:34:04 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-23 01:34:04 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-23 01:34:04 (4242) [INFO]         or
* 2023-11-23 01:34:04 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-23 01:34:04 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-23 01:34:04 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-23 01:34:04 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-23 01:34:04 (4242) [INFO]         compromise:
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-23 01:34:04 (4242) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-23 01:34:04 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-23 01:34:04 (4259) [INFO] 
* 2023-11-23 01:34:04 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-23 01:34:04 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-23 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-23 01:34:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-23 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-23 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-23 01:34:06 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-23 01:34:06 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-23 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-23 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-23 01:34:06 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-23 01:34:06 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-23 01:34:06 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-23 01:34:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-23 01:34:10 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-23 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-23 01:34:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-23 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-23 01:34:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-23 01:34:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MmccTYfkFg/ea_profile.json
* 2023-11-23 01:34:15 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MmccTYfkFg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-23 01:34:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-24 01:33:32 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-24 01:33:32 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-24 01:33:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-24 01:33:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-24 01:33:32 (4229) [INFO] 
* 2023-11-24 01:33:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-24 01:33:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-24 01:33:33 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-24 01:33:33 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-24 01:33:33 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-24 01:33:33 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-24 01:33:33 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-24 01:33:33 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-24 01:33:33 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-24 01:33:33 (4259) [INFO] 
* 2023-11-24 01:33:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-24 01:33:33 (4229) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-24 01:33:44 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-24 01:33:44 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-24 01:33:44 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-24 01:33:44 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-24 01:33:44 (4242) [INFO] Trying other mirror.
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-24 01:33:44 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-24 01:33:44 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-24 01:33:44 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-24 01:33:44 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-24 01:33:44 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-24 01:33:44 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-24 01:33:44 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-24 01:33:44 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-24 01:33:44 (4242) [INFO]         or
* 2023-11-24 01:33:44 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-24 01:33:44 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-24 01:33:44 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-24 01:33:44 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-24 01:33:44 (4242) [INFO]         compromise:
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-24 01:33:44 (4242) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-24 01:33:44 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-24 01:33:44 (4259) [INFO] 
* 2023-11-24 01:33:44 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-24 01:33:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-24 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-24 01:33:46 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-24 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-24 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-24 01:33:46 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-24 01:33:46 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-24 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-24 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-24 01:33:46 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-24 01:33:46 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-24 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-24 01:33:48 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-24 01:33:48 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-24 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-24 01:33:48 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-24 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-24 01:33:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-24 01:33:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3dDaDV6lVU/ea_profile.json
* 2023-11-24 01:33:51 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3dDaDV6lVU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-24 01:33:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-25 01:35:08 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-25 01:35:09 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-25 01:35:09 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-25 01:35:09 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-25 01:35:09 (4229) [INFO] 
* 2023-11-25 01:35:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-25 01:35:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-25 01:35:09 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-25 01:35:09 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-25 01:35:09 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-25 01:35:09 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-25 01:35:09 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-25 01:35:09 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-25 01:35:09 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-25 01:35:09 (4259) [INFO] 
* 2023-11-25 01:35:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-25 01:35:09 (4229) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-25 01:35:21 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-25 01:35:21 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-25 01:35:21 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-25 01:35:21 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-25 01:35:21 (4242) [INFO] Trying other mirror.
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-25 01:35:21 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-25 01:35:21 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-25 01:35:21 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-25 01:35:21 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-25 01:35:21 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-25 01:35:21 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-25 01:35:21 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-25 01:35:21 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-25 01:35:21 (4242) [INFO]         or
* 2023-11-25 01:35:21 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-25 01:35:21 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-25 01:35:21 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-25 01:35:21 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-25 01:35:21 (4242) [INFO]         compromise:
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-25 01:35:21 (4242) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-25 01:35:21 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-25 01:35:21 (4259) [INFO] 
* 2023-11-25 01:35:21 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-25 01:35:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-25 01:35:21 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-25 01:35:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-25 01:35:23 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-25 01:35:23 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-25 01:35:23 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-25 01:35:23 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-25 01:35:23 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-25 01:35:23 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-25 01:35:23 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-25 01:35:23 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-25 01:35:23 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-25 01:35:28 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-25 01:35:28 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-25 01:35:28 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-25 01:35:28 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-25 01:35:28 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-25 01:35:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-25 01:35:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f7x8NXxBNf/ea_profile.json
* 2023-11-25 01:35:34 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f7x8NXxBNf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-25 01:35:34 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-26 01:35:41 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-26 01:35:42 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-26 01:35:42 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-26 01:35:42 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-26 01:35:42 (4229) [INFO] 
* 2023-11-26 01:35:42 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-26 01:35:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-26 01:35:43 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-26 01:35:43 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-26 01:35:43 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-26 01:35:43 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-26 01:35:43 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-26 01:35:43 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-26 01:35:43 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-26 01:35:43 (4259) [INFO] 
* 2023-11-26 01:35:43 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-26 01:35:43 (4229) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-26 01:35:54 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-26 01:35:54 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-26 01:35:54 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-26 01:35:54 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-26 01:35:54 (4242) [INFO] Trying other mirror.
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-26 01:35:54 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-26 01:35:54 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-26 01:35:54 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-26 01:35:54 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-26 01:35:54 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-26 01:35:54 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-26 01:35:54 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-26 01:35:54 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-26 01:35:54 (4242) [INFO]         or
* 2023-11-26 01:35:54 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-26 01:35:54 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-26 01:35:54 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-26 01:35:54 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-26 01:35:54 (4242) [INFO]         compromise:
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-26 01:35:54 (4242) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-26 01:35:54 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-26 01:35:54 (4259) [INFO] 
* 2023-11-26 01:35:54 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-26 01:35:54 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-26 01:35:54 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-26 01:35:55 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-26 01:35:55 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-26 01:35:55 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-26 01:35:55 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-26 01:35:55 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-26 01:35:55 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-26 01:35:55 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-26 01:35:55 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-26 01:35:55 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-26 01:35:55 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-26 01:35:59 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-26 01:35:59 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-26 01:35:59 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-26 01:35:59 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-26 01:35:59 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-26 01:35:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-26 01:35:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jYDbaE2PjG/ea_profile.json
* 2023-11-26 01:36:04 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jYDbaE2PjG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-26 01:36:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-27 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-27 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-27 01:33:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-27 01:33:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-27 01:33:40 (4229) [INFO] 
* 2023-11-27 01:33:41 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-27 01:33:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-27 01:33:41 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-27 01:33:41 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-27 01:33:41 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-27 01:33:41 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-27 01:33:41 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-27 01:33:41 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-27 01:33:41 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-27 01:33:41 (4259) [INFO] 
* 2023-11-27 01:33:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-27 01:33:41 (4229) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-27 01:33:53 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-27 01:33:53 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-27 01:33:53 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-27 01:33:53 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-27 01:33:53 (4242) [INFO] Trying other mirror.
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-27 01:33:53 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-27 01:33:53 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-27 01:33:53 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-27 01:33:53 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-27 01:33:53 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-27 01:33:53 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-27 01:33:53 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-27 01:33:53 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-27 01:33:53 (4242) [INFO]         or
* 2023-11-27 01:33:53 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-27 01:33:53 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-27 01:33:53 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-27 01:33:53 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-27 01:33:53 (4242) [INFO]         compromise:
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-27 01:33:53 (4242) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-27 01:33:53 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-27 01:33:53 (4259) [INFO] 
* 2023-11-27 01:33:53 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-27 01:33:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-27 01:33:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-27 01:33:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-27 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-27 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-27 01:33:54 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-27 01:33:54 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-27 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-27 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-27 01:33:54 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-27 01:33:54 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-27 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-27 01:33:59 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-27 01:33:59 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-27 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-27 01:33:59 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-27 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-27 01:33:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-27 01:33:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vmmRXDh0UX/ea_profile.json
* 2023-11-27 01:34:04 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vmmRXDh0UX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-27 01:34:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-28 01:33:50 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-28 01:33:50 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-28 01:33:50 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-28 01:33:50 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-28 01:33:50 (4229) [INFO] 
* 2023-11-28 01:33:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-28 01:33:51 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-28 01:33:51 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-28 01:33:51 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-28 01:33:51 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-28 01:33:51 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-28 01:33:51 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-28 01:33:51 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-28 01:33:51 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-28 01:33:51 (4259) [INFO] 
* 2023-11-28 01:33:51 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-28 01:33:51 (4229) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-28 01:34:02 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-28 01:34:02 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-28 01:34:02 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-28 01:34:02 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-28 01:34:02 (4242) [INFO] Trying other mirror.
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-28 01:34:02 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-28 01:34:02 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-28 01:34:02 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-28 01:34:02 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-28 01:34:02 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-28 01:34:02 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-28 01:34:02 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-28 01:34:02 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-28 01:34:02 (4242) [INFO]         or
* 2023-11-28 01:34:02 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-28 01:34:02 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-28 01:34:02 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-28 01:34:02 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-28 01:34:02 (4242) [INFO]         compromise:
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-28 01:34:02 (4242) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-28 01:34:02 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-28 01:34:02 (4259) [INFO] 
* 2023-11-28 01:34:02 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-28 01:34:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-28 01:34:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-28 01:34:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-28 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-28 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-28 01:34:03 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-28 01:34:03 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-28 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-28 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-28 01:34:03 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-28 01:34:03 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-28 01:34:03 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-28 01:34:08 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-28 01:34:08 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-28 01:34:08 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-28 01:34:08 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-28 01:34:08 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-28 01:34:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-28 01:34:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zsLEZX3dBM/ea_profile.json
* 2023-11-28 01:34:12 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zsLEZX3dBM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-28 01:34:12 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-29 01:33:39 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-29 01:33:39 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-29 01:33:39 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-29 01:33:39 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-29 01:33:39 (4229) [INFO] 
* 2023-11-29 01:33:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-29 01:33:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-29 01:33:40 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-29 01:33:40 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-29 01:33:40 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-29 01:33:40 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-29 01:33:40 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-29 01:33:40 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-29 01:33:40 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-29 01:33:40 (4259) [INFO] 
* 2023-11-29 01:33:40 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-29 01:33:40 (4229) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-29 01:33:51 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-29 01:33:51 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-29 01:33:51 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-29 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-29 01:33:51 (4242) [INFO] Trying other mirror.
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-29 01:33:51 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-29 01:33:51 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-29 01:33:51 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-29 01:33:51 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-29 01:33:51 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-29 01:33:51 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-29 01:33:51 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-29 01:33:51 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-29 01:33:51 (4242) [INFO]         or
* 2023-11-29 01:33:51 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-29 01:33:51 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-29 01:33:51 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-29 01:33:51 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-29 01:33:51 (4242) [INFO]         compromise:
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-29 01:33:51 (4242) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-29 01:33:51 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-29 01:33:51 (4259) [INFO] 
* 2023-11-29 01:33:51 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-29 01:33:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-29 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-29 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-29 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-29 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-29 01:33:52 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-29 01:33:52 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-29 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-29 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-29 01:33:52 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-29 01:33:52 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-29 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-29 01:33:55 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-29 01:33:55 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-29 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-29 01:33:55 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-29 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-29 01:33:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-29 01:33:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GLrRJvUehO/ea_profile.json
* 2023-11-29 01:33:59 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GLrRJvUehO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-29 01:33:59 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-30 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-11-30 01:33:45 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-11-30 01:33:45 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-30 01:33:45 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-30 01:33:45 (4229) [INFO] 
* 2023-11-30 01:33:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-30 01:33:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-11-30 01:33:45 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-11-30 01:33:45 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-11-30 01:33:45 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-11-30 01:33:45 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-11-30 01:33:45 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-11-30 01:33:45 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-11-30 01:33:45 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-11-30 01:33:45 (4259) [INFO] 
* 2023-11-30 01:33:45 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-30 01:33:45 (4229) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-11-30 01:33:56 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-11-30 01:33:56 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-11-30 01:33:56 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-11-30 01:33:56 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-30 01:33:56 (4242) [INFO] Trying other mirror.
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-11-30 01:33:56 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-30 01:33:56 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-30 01:33:56 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-30 01:33:56 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-30 01:33:56 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-30 01:33:56 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-30 01:33:56 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-30 01:33:56 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-11-30 01:33:56 (4242) [INFO]         or
* 2023-11-30 01:33:56 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-30 01:33:56 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-30 01:33:56 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-30 01:33:56 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-30 01:33:56 (4242) [INFO]         compromise:
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-11-30 01:33:56 (4242) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-11-30 01:33:56 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-30 01:33:56 (4259) [INFO] 
* 2023-11-30 01:33:56 (4242) [INFO] Is this ok [y/N]: 
* 2023-11-30 01:33:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-30 01:33:56 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-30 01:33:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-11-30 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-11-30 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-11-30 01:33:59 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-11-30 01:33:59 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-11-30 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-11-30 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-11-30 01:33:59 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-11-30 01:33:59 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-11-30 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-11-30 01:34:03 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-30 01:34:03 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-11-30 01:34:03 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-30 01:34:03 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-11-30 01:34:03 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-11-30 01:34:03 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-30 01:34:03 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1ibXY3NwBi/ea_profile.json
* 2023-11-30 01:34:10 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1ibXY3NwBi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-30 01:34:10 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-01 01:33:50 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-01 01:33:50 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-01 01:33:50 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-01 01:33:50 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-01 01:33:50 (4229) [INFO] 
* 2023-12-01 01:33:51 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-01 01:33:51 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-01 01:33:51 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-01 01:33:51 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-01 01:33:51 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-01 01:33:51 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-01 01:33:51 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-01 01:33:51 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-01 01:33:51 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-01 01:33:51 (4259) [INFO] 
* 2023-12-01 01:33:51 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-01 01:33:51 (4229) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-01 01:34:07 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-01 01:34:07 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-01 01:34:07 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-01 01:34:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-01 01:34:07 (4242) [INFO] Trying other mirror.
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-01 01:34:07 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-01 01:34:07 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-01 01:34:07 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-01 01:34:07 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-01 01:34:07 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-01 01:34:07 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-01 01:34:07 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-01 01:34:07 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-01 01:34:07 (4242) [INFO]         or
* 2023-12-01 01:34:07 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-01 01:34:07 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-01 01:34:07 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-01 01:34:07 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-01 01:34:07 (4242) [INFO]         compromise:
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-01 01:34:07 (4242) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-01 01:34:07 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-01 01:34:07 (4259) [INFO] 
* 2023-12-01 01:34:07 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-01 01:34:07 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-01 01:34:07 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-01 01:34:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-01 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-01 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-01 01:34:08 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-01 01:34:08 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-01 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-01 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-01 01:34:08 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-01 01:34:08 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-01 01:34:08 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-01 01:34:12 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-01 01:34:12 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-01 01:34:12 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-01 01:34:12 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-01 01:34:12 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-01 01:34:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-01 01:34:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VAopTE4rdo/ea_profile.json
* 2023-12-01 01:34:16 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VAopTE4rdo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-01 01:34:16 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-02 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-02 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-02 01:34:26 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-02 01:34:26 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-02 01:34:26 (4229) [INFO] 
* 2023-12-02 01:34:26 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-02 01:34:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-02 01:34:27 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-02 01:34:27 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-02 01:34:27 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-02 01:34:27 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-02 01:34:27 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-02 01:34:27 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-02 01:34:27 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-02 01:34:27 (4259) [INFO] 
* 2023-12-02 01:34:27 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-02 01:34:27 (4229) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-02 01:34:37 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-02 01:34:37 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-02 01:34:37 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-02 01:34:37 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-02 01:34:37 (4242) [INFO] Trying other mirror.
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-02 01:34:37 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-02 01:34:37 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-02 01:34:37 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-02 01:34:37 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-02 01:34:37 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-02 01:34:37 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-02 01:34:37 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-02 01:34:37 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-02 01:34:37 (4242) [INFO]         or
* 2023-12-02 01:34:37 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-02 01:34:37 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-02 01:34:37 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-02 01:34:37 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-02 01:34:37 (4242) [INFO]         compromise:
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-02 01:34:37 (4242) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-02 01:34:37 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-02 01:34:37 (4259) [INFO] 
* 2023-12-02 01:34:37 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-02 01:34:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-02 01:34:37 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-02 01:34:39 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-02 01:34:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-02 01:34:39 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-02 01:34:39 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-02 01:34:39 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-02 01:34:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-02 01:34:39 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-02 01:34:39 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-02 01:34:39 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-02 01:34:39 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-02 01:34:43 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-02 01:34:43 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-02 01:34:43 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-02 01:34:43 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-02 01:34:43 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-02 01:34:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-02 01:34:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0E3P8qlj5e/ea_profile.json
* 2023-12-02 01:34:46 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0E3P8qlj5e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-02 01:34:46 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-03 01:34:37 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-03 01:34:37 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-03 01:34:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-03 01:34:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-03 01:34:38 (4229) [INFO] 
* 2023-12-03 01:34:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-03 01:34:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-03 01:34:38 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-03 01:34:38 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-03 01:34:38 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-03 01:34:38 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-03 01:34:38 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-03 01:34:38 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-03 01:34:38 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-03 01:34:38 (4259) [INFO] 
* 2023-12-03 01:34:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-03 01:34:38 (4229) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-03 01:34:49 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-03 01:34:49 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-03 01:34:49 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-03 01:34:49 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-03 01:34:49 (4242) [INFO] Trying other mirror.
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-03 01:34:49 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-03 01:34:49 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-03 01:34:49 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-03 01:34:49 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-03 01:34:49 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-03 01:34:49 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-03 01:34:49 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-03 01:34:49 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-03 01:34:49 (4242) [INFO]         or
* 2023-12-03 01:34:49 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-03 01:34:49 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-03 01:34:49 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-03 01:34:49 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-03 01:34:49 (4242) [INFO]         compromise:
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-03 01:34:49 (4242) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-03 01:34:49 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-03 01:34:49 (4259) [INFO] 
* 2023-12-03 01:34:49 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-03 01:34:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-03 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-03 01:34:50 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-03 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-03 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-03 01:34:50 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-03 01:34:50 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-03 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-03 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-03 01:34:50 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-03 01:34:50 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-03 01:34:50 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-03 01:34:53 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-03 01:34:53 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-03 01:34:53 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-03 01:34:53 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-03 01:34:53 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-03 01:34:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-03 01:34:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NQRXz2NgTQ/ea_profile.json
* 2023-12-03 01:34:57 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NQRXz2NgTQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-03 01:34:57 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-04 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-04 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2023-12-04 01:33:58 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-04 01:33:58 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-04 01:33:58 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-04 01:33:58 (4229) [INFO] 
* 2023-12-04 01:33:58 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-04 01:33:58 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-04 01:33:58 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-04 01:33:58 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-04 01:33:58 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-04 01:33:58 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-04 01:33:58 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-04 01:33:58 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-04 01:33:58 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-04 01:33:58 (4259) [INFO] 
* 2023-12-04 01:33:58 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-04 01:33:58 (4229) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-04 01:34:09 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-04 01:34:09 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-04 01:34:09 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-04 01:34:09 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-04 01:34:09 (4242) [INFO] Trying other mirror.
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-04 01:34:09 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-04 01:34:09 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-04 01:34:09 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-04 01:34:09 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-04 01:34:09 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-04 01:34:09 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-04 01:34:09 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-04 01:34:09 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-04 01:34:09 (4242) [INFO]         or
* 2023-12-04 01:34:09 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-04 01:34:09 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-04 01:34:09 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-04 01:34:09 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-04 01:34:09 (4242) [INFO]         compromise:
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-04 01:34:09 (4242) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-04 01:34:09 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-04 01:34:09 (4259) [INFO] 
* 2023-12-04 01:34:09 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-04 01:34:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-04 01:34:09 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-04 01:34:10 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-04 01:34:10 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-04 01:34:10 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-04 01:34:10 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-04 01:34:10 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-04 01:34:10 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-04 01:34:10 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-04 01:34:10 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-04 01:34:10 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-04 01:34:10 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-04 01:34:17 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-04 01:34:17 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-04 01:34:17 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-04 01:34:17 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-04 01:34:17 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-04 01:34:17 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-04 01:34:17 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pQAxjOecMi/ea_profile.json
* 2023-12-04 01:34:21 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pQAxjOecMi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-04 01:34:21 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-05 01:33:35 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-05 01:33:35 (155) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2023-12-05 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-05 01:33:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-05 01:33:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-05 01:33:36 (4229) [INFO] 
* 2023-12-05 01:33:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-05 01:33:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-05 01:33:36 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-05 01:33:36 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-05 01:33:36 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-05 01:33:36 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-05 01:33:36 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-05 01:33:36 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-05 01:33:36 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-05 01:33:36 (4259) [INFO] 
* 2023-12-05 01:33:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-05 01:33:36 (4229) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-05 01:33:45 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-05 01:33:45 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-05 01:33:45 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-05 01:33:45 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-05 01:33:45 (4242) [INFO] Trying other mirror.
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-05 01:33:45 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-05 01:33:45 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-05 01:33:45 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-05 01:33:45 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-05 01:33:45 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-05 01:33:45 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-05 01:33:45 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-05 01:33:45 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-05 01:33:45 (4242) [INFO]         or
* 2023-12-05 01:33:45 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-05 01:33:45 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-05 01:33:45 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-05 01:33:45 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-05 01:33:45 (4242) [INFO]         compromise:
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-05 01:33:45 (4242) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-05 01:33:45 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-05 01:33:45 (4259) [INFO] 
* 2023-12-05 01:33:45 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-05 01:33:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-05 01:33:45 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-05 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-05 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-05 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-05 01:33:47 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-05 01:33:47 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-05 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-05 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-05 01:33:47 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-05 01:33:47 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-05 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-05 01:33:50 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-05 01:33:50 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-05 01:33:50 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-05 01:33:50 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-05 01:33:50 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-05 01:33:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-05 01:33:50 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ae1BIkFQGg/ea_profile.json
* 2023-12-05 01:33:54 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ae1BIkFQGg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-05 01:33:54 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-06 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-06 01:33:44 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-06 01:33:44 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-06 01:33:44 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-06 01:33:44 (4229) [INFO] 
* 2023-12-06 01:33:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-06 01:33:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-06 01:33:45 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-06 01:33:45 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-06 01:33:45 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-06 01:33:45 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-06 01:33:45 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-06 01:33:45 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-06 01:33:45 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-06 01:33:45 (4259) [INFO] 
* 2023-12-06 01:33:45 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-06 01:33:45 (4229) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-06 01:34:01 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-06 01:34:01 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-06 01:34:01 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-06 01:34:01 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-06 01:34:01 (4242) [INFO] Trying other mirror.
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-06 01:34:01 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-06 01:34:01 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-06 01:34:01 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-06 01:34:01 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-06 01:34:01 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-06 01:34:01 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-06 01:34:01 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-06 01:34:01 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-06 01:34:01 (4242) [INFO]         or
* 2023-12-06 01:34:01 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-06 01:34:01 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-06 01:34:01 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-06 01:34:01 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-06 01:34:01 (4242) [INFO]         compromise:
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-06 01:34:01 (4242) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-06 01:34:01 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-06 01:34:01 (4259) [INFO] 
* 2023-12-06 01:34:01 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-06 01:34:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-06 01:34:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-06 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-06 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-06 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-06 01:34:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-06 01:34:04 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-06 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-06 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-06 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-06 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-06 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-06 01:34:09 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-06 01:34:09 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-06 01:34:09 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-06 01:34:09 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-06 01:34:09 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-06 01:34:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-06 01:34:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zmYxloDK9o/ea_profile.json
* 2023-12-06 01:34:15 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zmYxloDK9o/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-06 01:34:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-07 01:33:46 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-07 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-07 01:33:47 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-07 01:33:47 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-07 01:33:47 (4229) [INFO] 
* 2023-12-07 01:33:47 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-07 01:33:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-07 01:33:47 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-07 01:33:47 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-07 01:33:47 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-07 01:33:47 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-07 01:33:47 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-07 01:33:47 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-07 01:33:47 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-07 01:33:47 (4259) [INFO] 
* 2023-12-07 01:33:47 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-07 01:33:47 (4229) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-07 01:34:02 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-07 01:34:02 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-07 01:34:02 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-07 01:34:02 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-07 01:34:02 (4242) [INFO] Trying other mirror.
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-07 01:34:02 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-07 01:34:02 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-07 01:34:02 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-07 01:34:02 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-07 01:34:02 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-07 01:34:02 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-07 01:34:02 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-07 01:34:02 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-07 01:34:02 (4242) [INFO]         or
* 2023-12-07 01:34:02 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-07 01:34:02 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-07 01:34:02 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-07 01:34:02 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-07 01:34:02 (4242) [INFO]         compromise:
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-07 01:34:02 (4242) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-07 01:34:02 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-07 01:34:02 (4259) [INFO] 
* 2023-12-07 01:34:02 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-07 01:34:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-07 01:34:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-07 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-07 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-07 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-07 01:34:04 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-07 01:34:04 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-07 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-07 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-07 01:34:04 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-07 01:34:04 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-07 01:34:04 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-07 01:34:20 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-07 01:34:20 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-07 01:34:20 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-07 01:34:20 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-07 01:34:20 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-07 01:34:20 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-07 01:34:20 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oLLZS7OH7m/ea_profile.json
* 2023-12-07 01:34:25 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oLLZS7OH7m/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-07 01:34:25 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-08 01:46:54 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-08 01:46:54 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-08 01:46:54 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-08 01:46:54 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-08 01:46:54 (4229) [INFO] 
* 2023-12-08 01:46:55 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-08 01:46:55 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-08 01:46:55 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-08 01:46:55 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-08 01:46:55 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-08 01:46:55 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-08 01:46:55 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-08 01:46:55 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-08 01:46:55 (4242) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2023-12-08 01:46:55 (4259) [INFO] 
* 2023-12-08 01:46:55 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-08 01:46:55 (4229) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-08 01:47:11 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-08 01:47:11 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-08 01:47:11 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-08 01:47:11 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-08 01:47:11 (4242) [INFO] Trying other mirror.
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-08 01:47:11 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-08 01:47:11 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-08 01:47:11 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-08 01:47:11 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-08 01:47:11 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-08 01:47:11 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-08 01:47:11 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-08 01:47:11 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-08 01:47:11 (4242) [INFO]         or
* 2023-12-08 01:47:11 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-08 01:47:11 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-08 01:47:11 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-08 01:47:11 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-08 01:47:11 (4242) [INFO]         compromise:
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-08 01:47:11 (4242) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-08 01:47:11 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-08 01:47:11 (4259) [INFO] 
* 2023-12-08 01:47:11 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-08 01:47:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-08 01:47:11 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-08 01:47:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-08 01:47:12 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-08 01:47:12 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-08 01:47:12 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-08 01:47:12 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-08 01:47:12 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-08 01:47:12 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-08 01:47:12 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-08 01:47:12 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-08 01:47:12 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-08 01:47:19 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-08 01:47:19 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-08 01:47:19 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-08 01:47:19 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-08 01:47:19 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-08 01:47:19 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-08 01:47:19 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wRD0kzGd4V/ea_profile.json
* 2023-12-08 01:47:23 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wRD0kzGd4V/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-08 01:47:23 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-09 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-09 01:34:26 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-09 01:34:26 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-09 01:34:26 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-09 01:34:26 (4229) [INFO] 
* 2023-12-09 01:34:27 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-09 01:34:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-09 01:34:27 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-09 01:34:27 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-09 01:34:27 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-09 01:34:27 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-09 01:34:27 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-09 01:34:27 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-09 01:34:27 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-09 01:34:27 (4259) [INFO] 
* 2023-12-09 01:34:27 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-09 01:34:27 (4229) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-09 01:34:47 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-09 01:34:47 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-09 01:34:47 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-09 01:34:47 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-09 01:34:47 (4242) [INFO] Trying other mirror.
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-09 01:34:47 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-09 01:34:47 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-09 01:34:47 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-09 01:34:47 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-09 01:34:47 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-09 01:34:47 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-09 01:34:47 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-09 01:34:47 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-09 01:34:47 (4242) [INFO]         or
* 2023-12-09 01:34:47 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-09 01:34:47 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-09 01:34:47 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-09 01:34:47 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-09 01:34:47 (4242) [INFO]         compromise:
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-09 01:34:47 (4242) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-09 01:34:47 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-09 01:34:47 (4259) [INFO] 
* 2023-12-09 01:34:47 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-09 01:34:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-09 01:34:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-09 01:34:49 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-09 01:34:49 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-09 01:34:49 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-09 01:34:49 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-09 01:34:49 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-09 01:34:49 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-09 01:34:49 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-09 01:34:49 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-09 01:34:49 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-09 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-09 01:34:56 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-09 01:34:56 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-09 01:34:56 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-09 01:34:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-09 01:34:56 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-09 01:34:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-09 01:34:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F9CmDZL9np/ea_profile.json
* 2023-12-09 01:35:04 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F9CmDZL9np/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-09 01:35:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-10 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-10 01:34:49 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-10 01:34:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-10 01:34:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-10 01:34:49 (4229) [INFO] 
* 2023-12-10 01:34:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-10 01:34:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-10 01:34:50 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-10 01:34:50 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-10 01:34:50 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-10 01:34:50 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-10 01:34:50 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-10 01:34:50 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-10 01:34:50 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-10 01:34:50 (4259) [INFO] 
* 2023-12-10 01:34:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-10 01:34:50 (4229) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-10 01:35:00 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-10 01:35:00 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-10 01:35:00 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-10 01:35:00 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-10 01:35:00 (4242) [INFO] Trying other mirror.
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-10 01:35:00 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-10 01:35:00 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-10 01:35:00 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-10 01:35:00 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-10 01:35:00 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-10 01:35:00 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-10 01:35:00 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-10 01:35:00 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-10 01:35:00 (4242) [INFO]         or
* 2023-12-10 01:35:00 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-10 01:35:00 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-10 01:35:00 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-10 01:35:00 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-10 01:35:00 (4242) [INFO]         compromise:
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-10 01:35:00 (4242) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-10 01:35:00 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-10 01:35:00 (4259) [INFO] 
* 2023-12-10 01:35:00 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-10 01:35:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-10 01:35:00 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-10 01:35:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-10 01:35:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-10 01:35:01 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-10 01:35:01 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-10 01:35:01 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-10 01:35:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-10 01:35:01 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-10 01:35:01 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-10 01:35:01 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-10 01:35:01 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-10 01:35:08 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-10 01:35:08 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-10 01:35:08 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-10 01:35:08 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-10 01:35:08 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-10 01:35:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-10 01:35:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UeOlx2ctzs/ea_profile.json
* 2023-12-10 01:35:15 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UeOlx2ctzs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-10 01:35:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-11 01:34:08 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-11 01:34:08 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-11 01:34:08 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-11 01:34:08 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-11 01:34:08 (4229) [INFO] 
* 2023-12-11 01:34:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-11 01:34:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-11 01:34:09 (4242) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-11 01:34:09 (4242) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-11 01:34:09 (4242) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-11 01:34:09 (4242) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-11 01:34:09 (4242) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-11 01:34:09 (4242) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-11 01:34:09 (4242) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-11 01:34:09 (4259) [INFO] 
* 2023-12-11 01:34:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-11 01:34:09 (4229) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-11 01:34:20 (4242) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-11 01:34:20 (4242) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-11 01:34:20 (4242) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-11 01:34:20 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-11 01:34:20 (4242) [INFO] Trying other mirror.
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-11 01:34:20 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-11 01:34:20 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-11 01:34:20 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-11 01:34:20 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-11 01:34:20 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-11 01:34:20 (4242) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-11 01:34:20 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-11 01:34:20 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-11 01:34:20 (4242) [INFO]         or
* 2023-12-11 01:34:20 (4242) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-11 01:34:20 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-11 01:34:20 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-11 01:34:20 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-11 01:34:20 (4242) [INFO]         compromise:
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-11 01:34:20 (4242) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-11 01:34:20 (4242) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-11 01:34:20 (4259) [INFO] 
* 2023-12-11 01:34:20 (4242) [INFO] Is this ok [y/N]: 
* 2023-12-11 01:34:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-11 01:34:20 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-11 01:34:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-11 01:34:21 (1688) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-11 01:34:21 (1688) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-11 01:34:21 (1677) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-11 01:34:21 (1677) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-11 01:34:21 (1688) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-11 01:34:21 (1688) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-11 01:34:21 (1677) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-11 01:34:21 (1688) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-11 01:34:21 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-11 01:34:25 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-11 01:34:25 (1619) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-11 01:34:25 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-11 01:34:25 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-11 01:34:25 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-11 01:34:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-11 01:34:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WYCUfhtLvA/ea_profile.json
* 2023-12-11 01:34:29 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WYCUfhtLvA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-11 01:34:29 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-12 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-12 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-12 01:33:40 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-12 01:33:40 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-12 01:33:40 (4230) [INFO] 
* 2023-12-12 01:33:40 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-12 01:33:41 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-12 01:33:41 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-12 01:33:41 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-12 01:33:41 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-12 01:33:41 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-12 01:33:41 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-12 01:33:41 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-12 01:33:41 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-12 01:33:41 (4260) [INFO] 
* 2023-12-12 01:33:41 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-12 01:33:41 (4230) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-12 01:33:51 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-12 01:33:51 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-12 01:33:51 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-12 01:33:51 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-12 01:33:51 (4243) [INFO] Trying other mirror.
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-12 01:33:51 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-12 01:33:51 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-12 01:33:51 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-12 01:33:51 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-12 01:33:51 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-12 01:33:51 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-12 01:33:51 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-12 01:33:51 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-12 01:33:51 (4243) [INFO]         or
* 2023-12-12 01:33:51 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-12 01:33:51 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-12 01:33:51 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-12 01:33:51 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-12 01:33:51 (4243) [INFO]         compromise:
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-12 01:33:51 (4243) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-12 01:33:51 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-12 01:33:51 (4260) [INFO] 
* 2023-12-12 01:33:51 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-12 01:33:51 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-12 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-12 01:33:52 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-12 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-12 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-12 01:33:52 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-12 01:33:52 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-12 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-12 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-12 01:33:52 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-12 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-12 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-12 01:33:55 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-12 01:33:55 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-12 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-12 01:33:55 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-12 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-12 01:33:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-12 01:33:55 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oNihCIoH3P/ea_profile.json
* 2023-12-12 01:33:59 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oNihCIoH3P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-12 01:33:59 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-13 01:33:39 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-13 01:33:40 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-13 01:33:40 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-13 01:33:40 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-13 01:33:40 (4230) [INFO] 
* 2023-12-13 01:33:40 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-13 01:33:40 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-13 01:33:40 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-13 01:33:40 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-13 01:33:40 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-13 01:33:40 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-13 01:33:40 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-13 01:33:40 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-13 01:33:40 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-13 01:33:40 (4260) [INFO] 
* 2023-12-13 01:33:40 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-13 01:33:40 (4230) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-13 01:33:51 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-13 01:33:51 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-13 01:33:51 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-13 01:33:51 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-13 01:33:51 (4243) [INFO] Trying other mirror.
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-13 01:33:51 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-13 01:33:51 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-13 01:33:51 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-13 01:33:51 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-13 01:33:51 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-13 01:33:51 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-13 01:33:51 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-13 01:33:51 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-13 01:33:51 (4243) [INFO]         or
* 2023-12-13 01:33:51 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-13 01:33:51 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-13 01:33:51 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-13 01:33:51 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-13 01:33:51 (4243) [INFO]         compromise:
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-13 01:33:51 (4243) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-13 01:33:51 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-13 01:33:51 (4260) [INFO] 
* 2023-12-13 01:33:51 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-13 01:33:51 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-13 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-13 01:33:52 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-13 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-13 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-13 01:33:52 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-13 01:33:52 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-13 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-13 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-13 01:33:52 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-13 01:33:52 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-13 01:33:52 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-13 01:33:55 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-13 01:33:55 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-13 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-13 01:33:55 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-13 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-13 01:33:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-13 01:33:55 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/caMNSCVSqo/ea_profile.json
* 2023-12-13 01:33:58 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/caMNSCVSqo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-13 01:33:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-14 01:34:16 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-14 01:34:16 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-14 01:34:16 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-14 01:34:16 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-14 01:34:16 (4230) [INFO] 
* 2023-12-14 01:34:16 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-14 01:34:17 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-14 01:34:17 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-14 01:34:17 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-14 01:34:17 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-14 01:34:17 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-14 01:34:17 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-14 01:34:17 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-14 01:34:17 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-14 01:34:17 (4260) [INFO] 
* 2023-12-14 01:34:17 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-14 01:34:17 (4230) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-14 01:34:30 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-14 01:34:30 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-14 01:34:30 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-14 01:34:30 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-14 01:34:30 (4243) [INFO] Trying other mirror.
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-14 01:34:30 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-14 01:34:30 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-14 01:34:30 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-14 01:34:30 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-14 01:34:30 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-14 01:34:30 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-14 01:34:30 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-14 01:34:30 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-14 01:34:30 (4243) [INFO]         or
* 2023-12-14 01:34:30 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-14 01:34:30 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-14 01:34:30 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-14 01:34:30 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-14 01:34:30 (4243) [INFO]         compromise:
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-14 01:34:30 (4243) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-14 01:34:30 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-14 01:34:30 (4260) [INFO] 
* 2023-12-14 01:34:30 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-14 01:34:30 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-14 01:34:30 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-14 01:34:31 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-14 01:34:31 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-14 01:34:31 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-14 01:34:31 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-14 01:34:31 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-14 01:34:31 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-14 01:34:31 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-14 01:34:31 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-14 01:34:31 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-14 01:34:31 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-14 01:34:35 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-14 01:34:35 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-14 01:34:35 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-14 01:34:35 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-14 01:34:35 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-14 01:34:35 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-14 01:34:35 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lK6m5gGx_y/ea_profile.json
* 2023-12-14 01:34:40 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lK6m5gGx_y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-14 01:34:40 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-15 01:33:38 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-15 01:33:39 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-15 01:33:39 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-15 01:33:39 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-15 01:33:39 (4230) [INFO] 
* 2023-12-15 01:33:40 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-15 01:33:40 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-15 01:33:40 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-15 01:33:40 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-15 01:33:40 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-15 01:33:40 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-15 01:33:40 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-15 01:33:40 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-15 01:33:40 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-15 01:33:40 (4260) [INFO] 
* 2023-12-15 01:33:40 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-15 01:33:40 (4230) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-15 01:33:55 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-15 01:33:55 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-15 01:33:55 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-15 01:33:55 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-15 01:33:55 (4243) [INFO] Trying other mirror.
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-15 01:33:55 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-15 01:33:55 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-15 01:33:55 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-15 01:33:55 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-15 01:33:55 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-15 01:33:55 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-15 01:33:55 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-15 01:33:55 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-15 01:33:55 (4243) [INFO]         or
* 2023-12-15 01:33:55 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-15 01:33:55 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-15 01:33:55 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-15 01:33:55 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-15 01:33:55 (4243) [INFO]         compromise:
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-15 01:33:55 (4243) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-15 01:33:55 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-15 01:33:55 (4260) [INFO] 
* 2023-12-15 01:33:55 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-15 01:33:55 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-15 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-15 01:33:57 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-15 01:33:57 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-15 01:33:57 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-15 01:33:57 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-15 01:33:57 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-15 01:33:57 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-15 01:33:57 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-15 01:33:57 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-15 01:33:57 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-15 01:33:57 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-15 01:34:00 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-15 01:34:00 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-15 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-15 01:34:00 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-15 01:34:00 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-15 01:34:00 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-15 01:34:00 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AWcV_8YWr1/ea_profile.json
* 2023-12-15 01:34:05 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AWcV_8YWr1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-15 01:34:05 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-16 01:34:21 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-16 01:34:21 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-12-16 01:34:22 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-16 01:34:22 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-16 01:34:22 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-16 01:34:22 (4230) [INFO] 
* 2023-12-16 01:34:22 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-16 01:34:22 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-16 01:34:22 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-16 01:34:22 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-16 01:34:22 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-16 01:34:22 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-16 01:34:22 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-16 01:34:22 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-16 01:34:22 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-16 01:34:22 (4260) [INFO] 
* 2023-12-16 01:34:22 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-16 01:34:22 (4230) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-16 01:34:33 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-16 01:34:33 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-16 01:34:33 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-16 01:34:33 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-16 01:34:33 (4243) [INFO] Trying other mirror.
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-16 01:34:33 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-16 01:34:33 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-16 01:34:33 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-16 01:34:33 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-16 01:34:33 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-16 01:34:33 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-16 01:34:33 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-16 01:34:33 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-16 01:34:33 (4243) [INFO]         or
* 2023-12-16 01:34:33 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-16 01:34:33 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-16 01:34:33 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-16 01:34:33 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-16 01:34:33 (4243) [INFO]         compromise:
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-16 01:34:33 (4243) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-16 01:34:33 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-16 01:34:33 (4260) [INFO] 
* 2023-12-16 01:34:33 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-16 01:34:33 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-16 01:34:33 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-16 01:34:34 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-16 01:34:34 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-16 01:34:34 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-16 01:34:34 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-16 01:34:34 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-16 01:34:34 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-16 01:34:34 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-16 01:34:34 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-16 01:34:34 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-16 01:34:34 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-16 01:34:39 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-16 01:34:39 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-16 01:34:39 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-16 01:34:39 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-16 01:34:39 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-16 01:34:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-16 01:34:39 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WJqe_RnP8z/ea_profile.json
* 2023-12-16 01:34:43 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WJqe_RnP8z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-16 01:34:43 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-17 01:34:24 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-17 01:34:24 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-12-17 01:34:25 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-17 01:34:25 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-17 01:34:25 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-17 01:34:25 (4230) [INFO] 
* 2023-12-17 01:34:25 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-17 01:34:25 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-17 01:34:25 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-17 01:34:25 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-17 01:34:25 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-17 01:34:25 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-17 01:34:25 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-17 01:34:25 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-17 01:34:25 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-17 01:34:25 (4260) [INFO] 
* 2023-12-17 01:34:25 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-17 01:34:25 (4230) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-17 01:34:37 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-17 01:34:37 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-17 01:34:37 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-17 01:34:37 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-17 01:34:37 (4243) [INFO] Trying other mirror.
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-17 01:34:37 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-17 01:34:37 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-17 01:34:37 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-17 01:34:37 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-17 01:34:37 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-17 01:34:37 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-17 01:34:37 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-17 01:34:37 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-17 01:34:37 (4243) [INFO]         or
* 2023-12-17 01:34:37 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-17 01:34:37 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-17 01:34:37 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-17 01:34:37 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-17 01:34:37 (4243) [INFO]         compromise:
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-17 01:34:37 (4243) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-17 01:34:37 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-17 01:34:37 (4260) [INFO] 
* 2023-12-17 01:34:37 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-17 01:34:37 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-17 01:34:37 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-17 01:34:39 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-17 01:34:39 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-17 01:34:39 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-17 01:34:39 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-17 01:34:39 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-17 01:34:39 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-17 01:34:39 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-17 01:34:39 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-17 01:34:39 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-17 01:34:39 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-17 01:34:43 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-17 01:34:43 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-17 01:34:43 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-17 01:34:43 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-17 01:34:43 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-17 01:34:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-17 01:34:43 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oZvoO9qIFb/ea_profile.json
* 2023-12-17 01:34:47 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oZvoO9qIFb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-17 01:34:47 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-18 01:33:35 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-18 01:33:35 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-12-18 01:33:36 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-18 01:33:36 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-18 01:33:36 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-18 01:33:36 (4230) [INFO] 
* 2023-12-18 01:33:36 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-18 01:33:36 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-18 01:33:36 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-18 01:33:36 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-18 01:33:36 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-18 01:33:36 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-18 01:33:36 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-18 01:33:36 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-18 01:33:37 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-18 01:33:37 (4260) [INFO] 
* 2023-12-18 01:33:37 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-18 01:33:37 (4230) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-18 01:33:47 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-18 01:33:47 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-18 01:33:47 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-18 01:33:47 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-18 01:33:47 (4243) [INFO] Trying other mirror.
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-18 01:33:47 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-18 01:33:47 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-18 01:33:47 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-18 01:33:47 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-18 01:33:47 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-18 01:33:47 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-18 01:33:47 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-18 01:33:47 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-18 01:33:47 (4243) [INFO]         or
* 2023-12-18 01:33:47 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-18 01:33:47 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-18 01:33:47 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-18 01:33:47 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-18 01:33:47 (4243) [INFO]         compromise:
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-18 01:33:47 (4243) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-18 01:33:47 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-18 01:33:47 (4260) [INFO] 
* 2023-12-18 01:33:47 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-18 01:33:47 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-18 01:33:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-18 01:33:48 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-18 01:33:48 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-18 01:33:48 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-18 01:33:48 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-18 01:33:48 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-18 01:33:48 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-18 01:33:48 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-18 01:33:48 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-18 01:33:48 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-18 01:33:48 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-18 01:33:51 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-18 01:33:51 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-18 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-18 01:33:51 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-18 01:33:51 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-18 01:33:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-18 01:33:51 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A4cOw_UUJI/ea_profile.json
* 2023-12-18 01:33:58 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A4cOw_UUJI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-18 01:33:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-19 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-19 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-12-19 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-19 01:33:42 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-19 01:33:42 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-19 01:33:42 (4230) [INFO] 
* 2023-12-19 01:33:42 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-19 01:33:43 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-19 01:33:43 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-19 01:33:43 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-19 01:33:43 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-19 01:33:43 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-19 01:33:43 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-19 01:33:43 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-19 01:33:43 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-19 01:33:43 (4260) [INFO] 
* 2023-12-19 01:33:43 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-19 01:33:43 (4230) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-19 01:33:54 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-19 01:33:54 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-19 01:33:54 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-19 01:33:54 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-19 01:33:54 (4243) [INFO] Trying other mirror.
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-19 01:33:54 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-19 01:33:54 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-19 01:33:54 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-19 01:33:54 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-19 01:33:54 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-19 01:33:54 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-19 01:33:54 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-19 01:33:54 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-19 01:33:54 (4243) [INFO]         or
* 2023-12-19 01:33:54 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-19 01:33:54 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-19 01:33:54 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-19 01:33:54 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-19 01:33:54 (4243) [INFO]         compromise:
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-19 01:33:54 (4243) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-19 01:33:54 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-19 01:33:54 (4260) [INFO] 
* 2023-12-19 01:33:54 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-19 01:33:54 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-19 01:33:54 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-19 01:33:55 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-19 01:33:55 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-19 01:33:55 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-19 01:33:55 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-19 01:33:55 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-19 01:33:55 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-19 01:33:55 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-19 01:33:55 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-19 01:33:55 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-19 01:33:55 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-19 01:33:59 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-19 01:33:59 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-19 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-19 01:33:59 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-19 01:33:59 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-19 01:33:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-19 01:33:59 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nMF9TZnKe9/ea_profile.json
* 2023-12-19 01:34:04 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nMF9TZnKe9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-19 01:34:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-20 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-20 01:33:42 (155) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-12-20 01:33:43 (155) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-20 01:33:43 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-20 01:33:43 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-20 01:33:43 (4230) [INFO] 
* 2023-12-20 01:33:43 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-20 01:33:44 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-20 01:33:44 (4243) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-20 01:33:44 (4243) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-20 01:33:44 (4243) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-20 01:33:44 (4243) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-20 01:33:44 (4243) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-20 01:33:44 (4243) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-20 01:33:44 (4243) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-20 01:33:44 (4260) [INFO] 
* 2023-12-20 01:33:44 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-20 01:33:44 (4230) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-20 01:34:01 (4243) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-20 01:34:01 (4243) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-20 01:34:01 (4243) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-20 01:34:01 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-20 01:34:01 (4243) [INFO] Trying other mirror.
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-20 01:34:01 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-20 01:34:01 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-20 01:34:01 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-20 01:34:01 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-20 01:34:01 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-20 01:34:01 (4243) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-20 01:34:01 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-20 01:34:01 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-20 01:34:01 (4243) [INFO]         or
* 2023-12-20 01:34:01 (4243) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-20 01:34:01 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-20 01:34:01 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-20 01:34:01 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-20 01:34:01 (4243) [INFO]         compromise:
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-20 01:34:01 (4243) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-20 01:34:01 (4243) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-20 01:34:01 (4260) [INFO] 
* 2023-12-20 01:34:01 (4243) [INFO] Is this ok [y/N]: 
* 2023-12-20 01:34:01 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-20 01:34:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-20 01:34:02 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-20 01:34:02 (1689) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-20 01:34:02 (1689) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-20 01:34:02 (1678) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-20 01:34:02 (1678) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-20 01:34:02 (1689) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-20 01:34:02 (1689) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-20 01:34:02 (1678) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-20 01:34:02 (1689) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-20 01:34:02 (155) [WARN] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-12-20 01:34:09 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-20 01:34:09 (1620) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-20 01:34:09 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-20 01:34:09 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-20 01:34:09 (155) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-20 01:34:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-20 01:34:10 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UhbqFam1_e/ea_profile.json
* 2023-12-20 01:34:16 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UhbqFam1_e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-20 01:34:16 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-21 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-21 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-12-21 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-21 01:34:03 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-21 01:34:03 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-21 01:34:03 (4251) [INFO] 
* 2023-12-21 01:34:04 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-21 01:34:04 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-21 01:34:04 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-21 01:34:04 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-21 01:34:04 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-21 01:34:04 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-21 01:34:04 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-21 01:34:04 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-21 01:34:04 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-21 01:34:04 (4281) [INFO] 
* 2023-12-21 01:34:04 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-21 01:34:04 (4251) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-21 01:34:16 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-21 01:34:16 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-21 01:34:16 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-21 01:34:16 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-21 01:34:16 (4264) [INFO] Trying other mirror.
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-21 01:34:16 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-21 01:34:16 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-21 01:34:16 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-21 01:34:16 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-21 01:34:16 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-21 01:34:16 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-21 01:34:16 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-21 01:34:16 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-21 01:34:16 (4264) [INFO]         or
* 2023-12-21 01:34:16 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-21 01:34:16 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-21 01:34:16 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-21 01:34:16 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-21 01:34:16 (4264) [INFO]         compromise:
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-21 01:34:16 (4264) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-21 01:34:16 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-21 01:34:16 (4281) [INFO] 
* 2023-12-21 01:34:16 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-21 01:34:16 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-21 01:34:16 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-21 01:34:17 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-21 01:34:17 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-21 01:34:17 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-21 01:34:17 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-21 01:34:17 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-21 01:34:17 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-21 01:34:17 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-21 01:34:17 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-21 01:34:17 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-21 01:34:21 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-21 01:34:21 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-21 01:34:21 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-21 01:34:21 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-21 01:34:21 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-21 01:34:21 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-21 01:34:21 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SxgETanDW2/ea_profile.json
* 2023-12-21 01:34:26 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SxgETanDW2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-21 01:34:26 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-22 01:34:01 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-22 01:34:01 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2023-12-22 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-22 01:34:02 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-22 01:34:02 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-22 01:34:02 (4251) [INFO] 
* 2023-12-22 01:34:02 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-22 01:34:02 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-22 01:34:02 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-22 01:34:02 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-22 01:34:02 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-22 01:34:02 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-22 01:34:02 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-22 01:34:02 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-22 01:34:02 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-22 01:34:02 (4281) [INFO] 
* 2023-12-22 01:34:02 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-22 01:34:02 (4251) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-22 01:34:20 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-22 01:34:20 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-22 01:34:20 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-22 01:34:20 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-22 01:34:20 (4264) [INFO] Trying other mirror.
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-22 01:34:20 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-22 01:34:20 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-22 01:34:20 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-22 01:34:20 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-22 01:34:20 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-22 01:34:20 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-22 01:34:20 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-22 01:34:20 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-22 01:34:20 (4264) [INFO]         or
* 2023-12-22 01:34:20 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-22 01:34:20 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-22 01:34:20 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-22 01:34:20 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-22 01:34:20 (4264) [INFO]         compromise:
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-22 01:34:20 (4264) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-22 01:34:20 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-22 01:34:20 (4281) [INFO] 
* 2023-12-22 01:34:20 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-22 01:34:20 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-22 01:34:20 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-22 01:34:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-22 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-22 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-22 01:34:21 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-22 01:34:21 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-22 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-22 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-22 01:34:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-22 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-22 01:34:25 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-22 01:34:25 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-22 01:34:25 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-22 01:34:25 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-22 01:34:25 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-22 01:34:25 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-22 01:34:25 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uY3zHmFKeQ/ea_profile.json
* 2023-12-22 01:34:42 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uY3zHmFKeQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-22 01:34:42 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-23 01:34:50 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-23 01:34:51 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-23 01:34:51 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-23 01:34:51 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-23 01:34:51 (4251) [INFO] 
* 2023-12-23 01:34:51 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-23 01:34:51 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-23 01:34:51 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-23 01:34:51 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-23 01:34:51 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-23 01:34:51 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-23 01:34:51 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-23 01:34:51 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-23 01:34:51 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-23 01:34:51 (4281) [INFO] 
* 2023-12-23 01:34:51 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-23 01:34:51 (4251) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-23 01:35:08 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-23 01:35:08 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-23 01:35:08 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-23 01:35:08 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-23 01:35:08 (4264) [INFO] Trying other mirror.
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-23 01:35:08 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-23 01:35:08 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-23 01:35:08 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-23 01:35:08 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-23 01:35:08 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-23 01:35:08 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-23 01:35:08 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-23 01:35:08 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-23 01:35:08 (4264) [INFO]         or
* 2023-12-23 01:35:08 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-23 01:35:08 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-23 01:35:08 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-23 01:35:08 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-23 01:35:08 (4264) [INFO]         compromise:
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-23 01:35:08 (4264) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-23 01:35:08 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-23 01:35:08 (4281) [INFO] 
* 2023-12-23 01:35:08 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-23 01:35:08 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-23 01:35:08 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-23 01:35:09 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-23 01:35:09 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-23 01:35:09 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-23 01:35:09 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-23 01:35:09 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-23 01:35:09 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-23 01:35:09 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-23 01:35:09 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-23 01:35:09 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-23 01:35:12 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-23 01:35:12 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-23 01:35:12 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-23 01:35:12 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-23 01:35:12 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-23 01:35:13 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-23 01:35:13 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4JxGoGhMJK/ea_profile.json
* 2023-12-23 01:35:16 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4JxGoGhMJK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-23 01:35:16 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-24 01:35:10 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-24 01:35:10 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-24 01:35:10 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-24 01:35:10 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-24 01:35:10 (4251) [INFO] 
* 2023-12-24 01:35:10 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-24 01:35:11 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-24 01:35:11 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-24 01:35:11 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-24 01:35:11 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-24 01:35:11 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-24 01:35:11 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-24 01:35:11 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-24 01:35:11 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-24 01:35:11 (4281) [INFO] 
* 2023-12-24 01:35:11 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-24 01:35:11 (4251) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-24 01:35:21 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-24 01:35:21 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-24 01:35:21 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-24 01:35:21 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-24 01:35:21 (4264) [INFO] Trying other mirror.
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-24 01:35:21 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-24 01:35:21 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-24 01:35:21 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-24 01:35:21 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-24 01:35:21 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-24 01:35:21 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-24 01:35:21 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-24 01:35:21 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-24 01:35:21 (4264) [INFO]         or
* 2023-12-24 01:35:21 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-24 01:35:21 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-24 01:35:21 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-24 01:35:21 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-24 01:35:21 (4264) [INFO]         compromise:
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-24 01:35:21 (4264) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-24 01:35:21 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-24 01:35:21 (4281) [INFO] 
* 2023-12-24 01:35:21 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-24 01:35:21 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-24 01:35:21 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-24 01:35:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-24 01:35:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-24 01:35:21 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-24 01:35:21 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-24 01:35:21 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-24 01:35:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-24 01:35:21 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-24 01:35:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-24 01:35:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-24 01:35:24 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-24 01:35:24 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-24 01:35:24 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-24 01:35:24 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-24 01:35:24 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-24 01:35:24 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-24 01:35:24 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Apg45FiM_N/ea_profile.json
* 2023-12-24 01:35:28 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Apg45FiM_N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-24 01:35:28 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-25 01:33:45 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-25 01:33:46 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-25 01:33:46 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-25 01:33:46 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-25 01:33:46 (4251) [INFO] 
* 2023-12-25 01:33:46 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-25 01:33:47 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-25 01:33:47 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-25 01:33:47 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-25 01:33:47 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-25 01:33:47 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-25 01:33:47 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-25 01:33:47 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-25 01:33:47 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-25 01:33:47 (4281) [INFO] 
* 2023-12-25 01:33:47 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-25 01:33:47 (4251) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-25 01:33:57 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-25 01:33:57 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-25 01:33:57 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-25 01:33:57 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-25 01:33:57 (4264) [INFO] Trying other mirror.
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-25 01:33:57 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-25 01:33:57 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-25 01:33:57 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-25 01:33:57 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-25 01:33:57 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-25 01:33:57 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-25 01:33:57 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-25 01:33:57 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-25 01:33:57 (4264) [INFO]         or
* 2023-12-25 01:33:57 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-25 01:33:57 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-25 01:33:57 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-25 01:33:57 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-25 01:33:57 (4264) [INFO]         compromise:
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-25 01:33:57 (4264) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-25 01:33:57 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-25 01:33:57 (4281) [INFO] 
* 2023-12-25 01:33:57 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-25 01:33:57 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-25 01:33:57 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-25 01:33:59 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-25 01:33:59 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-25 01:33:59 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-25 01:33:59 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-25 01:33:59 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-25 01:33:59 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-25 01:33:59 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-25 01:33:59 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-25 01:33:59 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-25 01:34:04 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-25 01:34:04 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-25 01:34:04 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-25 01:34:04 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-25 01:34:04 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-25 01:34:04 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-25 01:34:04 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ooHGm8AfnA/ea_profile.json
* 2023-12-25 01:34:10 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ooHGm8AfnA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-25 01:34:10 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-26 01:33:43 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-26 01:33:44 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-26 01:33:44 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-26 01:33:44 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-26 01:33:44 (4251) [INFO] 
* 2023-12-26 01:33:44 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-26 01:33:44 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-26 01:33:44 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-26 01:33:44 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-26 01:33:44 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-26 01:33:44 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-26 01:33:44 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-26 01:33:44 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-26 01:33:44 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-26 01:33:44 (4281) [INFO] 
* 2023-12-26 01:33:44 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-26 01:33:44 (4251) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-26 01:33:57 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-26 01:33:57 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-26 01:33:57 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-26 01:33:57 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-26 01:33:57 (4264) [INFO] Trying other mirror.
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-26 01:33:57 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-26 01:33:57 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-26 01:33:57 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-26 01:33:57 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-26 01:33:57 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-26 01:33:57 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-26 01:33:57 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-26 01:33:57 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-26 01:33:57 (4264) [INFO]         or
* 2023-12-26 01:33:57 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-26 01:33:57 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-26 01:33:57 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-26 01:33:57 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-26 01:33:57 (4264) [INFO]         compromise:
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-26 01:33:57 (4264) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-26 01:33:57 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-26 01:33:57 (4281) [INFO] 
* 2023-12-26 01:33:57 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-26 01:33:57 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-26 01:33:57 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-26 01:33:58 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-26 01:33:58 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-26 01:33:58 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-26 01:33:58 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-26 01:33:58 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-26 01:33:58 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-26 01:33:58 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-26 01:33:58 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-26 01:33:58 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-26 01:34:03 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-26 01:34:03 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-26 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-26 01:34:03 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-26 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-26 01:34:03 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-26 01:34:03 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WgYAbl8N08/ea_profile.json
* 2023-12-26 01:34:08 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WgYAbl8N08/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-26 01:34:08 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-27 01:33:46 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-27 01:33:47 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-27 01:33:47 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-27 01:33:47 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-27 01:33:47 (4251) [INFO] 
* 2023-12-27 01:33:47 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-27 01:33:47 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-27 01:33:47 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-27 01:33:47 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-27 01:33:47 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-27 01:33:47 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-27 01:33:47 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-27 01:33:47 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-27 01:33:47 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-27 01:33:47 (4281) [INFO] 
* 2023-12-27 01:33:47 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-27 01:33:47 (4251) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-27 01:34:02 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-27 01:34:02 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-27 01:34:02 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-27 01:34:02 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-27 01:34:02 (4264) [INFO] Trying other mirror.
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-27 01:34:02 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-27 01:34:02 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-27 01:34:02 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-27 01:34:02 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-27 01:34:02 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-27 01:34:02 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-27 01:34:02 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-27 01:34:02 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-27 01:34:02 (4264) [INFO]         or
* 2023-12-27 01:34:02 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-27 01:34:02 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-27 01:34:02 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-27 01:34:02 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-27 01:34:02 (4264) [INFO]         compromise:
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-27 01:34:02 (4264) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-27 01:34:02 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-27 01:34:02 (4281) [INFO] 
* 2023-12-27 01:34:02 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-27 01:34:02 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-27 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-27 01:34:03 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-27 01:34:03 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-27 01:34:03 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-27 01:34:03 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-27 01:34:03 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-27 01:34:03 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-27 01:34:03 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-27 01:34:03 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-27 01:34:03 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-27 01:34:09 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-27 01:34:09 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-27 01:34:09 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-27 01:34:09 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-27 01:34:09 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-27 01:34:09 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-27 01:34:09 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wJOzOp_cJ4/ea_profile.json
* 2023-12-27 01:34:15 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wJOzOp_cJ4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-27 01:34:15 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-28 01:33:40 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-28 01:33:41 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-28 01:33:41 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-28 01:33:41 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-28 01:33:41 (4251) [INFO] 
* 2023-12-28 01:33:41 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-28 01:33:41 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-28 01:33:41 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-28 01:33:41 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-28 01:33:41 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-28 01:33:41 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-28 01:33:41 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-28 01:33:41 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-28 01:33:41 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-28 01:33:41 (4281) [INFO] 
* 2023-12-28 01:33:41 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-28 01:33:41 (4251) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-28 01:33:52 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-28 01:33:52 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-28 01:33:52 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-28 01:33:52 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-28 01:33:52 (4264) [INFO] Trying other mirror.
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-28 01:33:52 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-28 01:33:52 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-28 01:33:52 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-28 01:33:52 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-28 01:33:52 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-28 01:33:52 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-28 01:33:52 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-28 01:33:52 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-28 01:33:52 (4264) [INFO]         or
* 2023-12-28 01:33:52 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-28 01:33:52 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-28 01:33:52 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-28 01:33:52 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-28 01:33:52 (4264) [INFO]         compromise:
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-28 01:33:52 (4264) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-28 01:33:52 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-28 01:33:52 (4281) [INFO] 
* 2023-12-28 01:33:52 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-28 01:33:52 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-28 01:33:52 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-28 01:33:54 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-28 01:33:54 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-28 01:33:54 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-28 01:33:54 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-28 01:33:54 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-28 01:33:54 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-28 01:33:54 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-28 01:33:54 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-28 01:33:54 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-28 01:33:57 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-28 01:33:57 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-28 01:33:57 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-28 01:33:57 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-28 01:33:57 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-28 01:33:57 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-28 01:33:57 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qbmaN951Mc/ea_profile.json
* 2023-12-28 01:34:01 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qbmaN951Mc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-28 01:34:01 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-29 01:34:21 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-29 01:34:23 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-29 01:34:23 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-29 01:34:23 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-29 01:34:23 (4251) [INFO] 
* 2023-12-29 01:34:23 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-29 01:34:23 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-29 01:34:23 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-29 01:34:23 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-29 01:34:23 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-29 01:34:23 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-29 01:34:23 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-29 01:34:23 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-29 01:34:23 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-29 01:34:23 (4281) [INFO] 
* 2023-12-29 01:34:23 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-29 01:34:23 (4251) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-29 01:34:36 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-29 01:34:36 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-29 01:34:36 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-29 01:34:36 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-29 01:34:36 (4264) [INFO] Trying other mirror.
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-29 01:34:36 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-29 01:34:36 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-29 01:34:36 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-29 01:34:36 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-29 01:34:36 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-29 01:34:36 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-29 01:34:36 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-29 01:34:36 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-29 01:34:36 (4264) [INFO]         or
* 2023-12-29 01:34:36 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-29 01:34:36 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-29 01:34:36 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-29 01:34:36 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-29 01:34:36 (4264) [INFO]         compromise:
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-29 01:34:36 (4264) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-29 01:34:36 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-29 01:34:36 (4281) [INFO] 
* 2023-12-29 01:34:36 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-29 01:34:36 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-29 01:34:36 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-29 01:34:38 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-29 01:34:38 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-29 01:34:38 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-29 01:34:38 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-29 01:34:38 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-29 01:34:38 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-29 01:34:38 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-29 01:34:38 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-29 01:34:38 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-29 01:34:42 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-29 01:34:42 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-29 01:34:42 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-29 01:34:42 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-29 01:34:42 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-29 01:34:43 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-29 01:34:43 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5wCJSTEDAK/ea_profile.json
* 2023-12-29 01:34:48 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5wCJSTEDAK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-29 01:34:48 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-30 01:35:26 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-30 01:35:27 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-30 01:35:27 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-30 01:35:27 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-30 01:35:27 (4251) [INFO] 
* 2023-12-30 01:35:27 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-30 01:35:28 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-30 01:35:28 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-30 01:35:28 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-30 01:35:28 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-30 01:35:28 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-30 01:35:28 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-30 01:35:28 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-30 01:35:28 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-30 01:35:28 (4281) [INFO] 
* 2023-12-30 01:35:28 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-30 01:35:28 (4251) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-30 01:35:42 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-30 01:35:42 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-30 01:35:42 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-30 01:35:42 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-30 01:35:42 (4264) [INFO] Trying other mirror.
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-30 01:35:42 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-30 01:35:42 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-30 01:35:42 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-30 01:35:42 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-30 01:35:42 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-30 01:35:42 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-30 01:35:42 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-30 01:35:42 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-30 01:35:42 (4264) [INFO]         or
* 2023-12-30 01:35:42 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-30 01:35:42 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-30 01:35:42 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-30 01:35:42 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-30 01:35:42 (4264) [INFO]         compromise:
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-30 01:35:42 (4264) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-30 01:35:42 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-30 01:35:42 (4281) [INFO] 
* 2023-12-30 01:35:42 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-30 01:35:42 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-30 01:35:42 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-30 01:35:44 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-30 01:35:44 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-30 01:35:44 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-30 01:35:44 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-30 01:35:44 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-30 01:35:44 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-30 01:35:44 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-30 01:35:44 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-30 01:35:44 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-30 01:35:50 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-30 01:35:50 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-30 01:35:50 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-30 01:35:50 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-30 01:35:50 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-30 01:35:51 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-30 01:35:51 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TG4300gouO/ea_profile.json
* 2023-12-30 01:35:56 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TG4300gouO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-30 01:35:56 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-31 01:35:10 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2023-12-31 01:35:11 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2023-12-31 01:35:11 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-31 01:35:11 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-31 01:35:11 (4251) [INFO] 
* 2023-12-31 01:35:11 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-31 01:35:11 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2023-12-31 01:35:11 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2023-12-31 01:35:11 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2023-12-31 01:35:11 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2023-12-31 01:35:11 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2023-12-31 01:35:11 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2023-12-31 01:35:11 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2023-12-31 01:35:12 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2023-12-31 01:35:12 (4281) [INFO] 
* 2023-12-31 01:35:12 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-31 01:35:12 (4251) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2023-12-31 01:35:22 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2023-12-31 01:35:22 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2023-12-31 01:35:22 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2023-12-31 01:35:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-31 01:35:22 (4264) [INFO] Trying other mirror.
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2023-12-31 01:35:22 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-31 01:35:22 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-31 01:35:22 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-31 01:35:22 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-31 01:35:22 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-31 01:35:22 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-31 01:35:22 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-31 01:35:22 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2023-12-31 01:35:22 (4264) [INFO]         or
* 2023-12-31 01:35:22 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-31 01:35:22 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-31 01:35:22 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-31 01:35:22 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-31 01:35:22 (4264) [INFO]         compromise:
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2023-12-31 01:35:22 (4264) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2023-12-31 01:35:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-31 01:35:22 (4281) [INFO] 
* 2023-12-31 01:35:22 (4264) [INFO] Is this ok [y/N]: 
* 2023-12-31 01:35:22 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-31 01:35:22 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-31 01:35:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2023-12-31 01:35:23 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2023-12-31 01:35:23 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2023-12-31 01:35:23 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2023-12-31 01:35:23 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2023-12-31 01:35:23 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2023-12-31 01:35:23 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2023-12-31 01:35:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2023-12-31 01:35:23 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2023-12-31 01:35:26 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-31 01:35:26 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2023-12-31 01:35:26 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-31 01:35:26 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2023-12-31 01:35:26 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2023-12-31 01:35:26 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-31 01:35:26 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZCL1Tp3tU4/ea_profile.json
* 2023-12-31 01:35:29 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZCL1Tp3tU4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-31 01:35:29 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-01 01:33:50 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-01 01:33:51 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-01 01:33:51 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-01 01:33:51 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-01 01:33:51 (4251) [INFO] 
* 2024-01-01 01:33:51 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-01 01:33:52 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-01 01:33:52 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-01 01:33:52 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-01 01:33:52 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-01 01:33:52 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-01 01:33:52 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-01 01:33:52 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-01 01:33:52 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-01 01:33:52 (4281) [INFO] 
* 2024-01-01 01:33:52 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-01 01:33:52 (4251) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-01 01:34:01 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-01 01:34:01 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-01 01:34:01 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-01 01:34:01 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-01 01:34:01 (4264) [INFO] Trying other mirror.
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-01 01:34:01 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-01 01:34:01 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-01 01:34:01 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-01 01:34:01 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-01 01:34:01 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-01 01:34:01 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-01 01:34:01 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-01 01:34:01 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-01 01:34:01 (4264) [INFO]         or
* 2024-01-01 01:34:01 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-01 01:34:01 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-01 01:34:01 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-01 01:34:01 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-01 01:34:01 (4264) [INFO]         compromise:
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-01 01:34:01 (4264) [INFO] 
* 2024-01-01 01:34:01 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-01 01:34:01 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-01 01:34:02 (4281) [INFO] 
* 2024-01-01 01:34:02 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-01 01:34:02 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-01 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-01 01:34:04 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-01 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-01 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-01 01:34:04 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-01 01:34:04 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-01 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-01 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-01 01:34:04 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-01 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-01 01:34:09 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-01 01:34:09 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-01 01:34:09 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-01 01:34:09 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-01 01:34:09 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-01 01:34:09 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-01 01:34:09 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9HCOrj2k1B/ea_profile.json
* 2024-01-01 01:34:15 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9HCOrj2k1B/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-01 01:34:15 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-02 01:34:01 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-02 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-02 01:34:02 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-02 01:34:02 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-02 01:34:02 (4251) [INFO] 
* 2024-01-02 01:34:03 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-02 01:34:03 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-02 01:34:03 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-02 01:34:03 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-02 01:34:03 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-02 01:34:03 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-02 01:34:03 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-02 01:34:03 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-02 01:34:03 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-02 01:34:03 (4281) [INFO] 
* 2024-01-02 01:34:03 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-02 01:34:03 (4251) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-02 01:34:19 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-02 01:34:19 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-02 01:34:19 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-02 01:34:19 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-02 01:34:19 (4264) [INFO] Trying other mirror.
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-02 01:34:19 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-02 01:34:19 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-02 01:34:19 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-02 01:34:19 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-02 01:34:19 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-02 01:34:19 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-02 01:34:19 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-02 01:34:19 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-02 01:34:19 (4264) [INFO]         or
* 2024-01-02 01:34:19 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-02 01:34:19 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-02 01:34:19 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-02 01:34:19 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-02 01:34:19 (4264) [INFO]         compromise:
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-02 01:34:19 (4264) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-02 01:34:19 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-02 01:34:19 (4281) [INFO] 
* 2024-01-02 01:34:19 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-02 01:34:19 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-02 01:34:19 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-02 01:34:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-02 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-02 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-02 01:34:21 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-02 01:34:21 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-02 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-02 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-02 01:34:21 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-02 01:34:21 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-02 01:34:27 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-02 01:34:27 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-02 01:34:27 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-02 01:34:27 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-02 01:34:27 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-02 01:34:27 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-02 01:34:27 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Gug8KTl5ea/ea_profile.json
* 2024-01-02 01:34:31 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Gug8KTl5ea/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-02 01:34:31 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-03 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-03 01:34:04 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-03 01:34:04 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-03 01:34:04 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-03 01:34:04 (4251) [INFO] 
* 2024-01-03 01:34:04 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-03 01:34:04 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-03 01:34:04 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-03 01:34:04 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-03 01:34:04 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-03 01:34:04 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-03 01:34:04 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-03 01:34:04 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-03 01:34:04 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-03 01:34:04 (4281) [INFO] 
* 2024-01-03 01:34:04 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-03 01:34:04 (4251) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-03 01:34:19 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-03 01:34:19 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-03 01:34:19 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-03 01:34:19 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-03 01:34:19 (4264) [INFO] Trying other mirror.
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-03 01:34:19 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-03 01:34:19 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-03 01:34:19 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-03 01:34:19 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-03 01:34:19 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-03 01:34:19 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-03 01:34:19 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-03 01:34:19 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-03 01:34:19 (4264) [INFO]         or
* 2024-01-03 01:34:19 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-03 01:34:19 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-03 01:34:19 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-03 01:34:19 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-03 01:34:19 (4264) [INFO]         compromise:
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-03 01:34:19 (4264) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-03 01:34:19 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-03 01:34:19 (4281) [INFO] 
* 2024-01-03 01:34:19 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-03 01:34:19 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-03 01:34:19 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-03 01:34:20 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-03 01:34:20 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-03 01:34:20 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-03 01:34:20 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-03 01:34:20 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-03 01:34:20 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-03 01:34:20 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-03 01:34:20 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-03 01:34:20 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-03 01:34:24 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-03 01:34:24 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-03 01:34:24 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-03 01:34:24 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-03 01:34:24 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-03 01:34:24 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-03 01:34:24 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bOGij20LFY/ea_profile.json
* 2024-01-03 01:34:29 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bOGij20LFY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-03 01:34:29 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-04 01:33:48 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-04 01:33:48 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-04 01:33:48 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-04 01:33:48 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-04 01:33:48 (4251) [INFO] 
* 2024-01-04 01:33:49 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-04 01:33:49 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-04 01:33:49 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-04 01:33:49 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-04 01:33:49 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-04 01:33:49 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-04 01:33:49 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-04 01:33:49 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-04 01:33:49 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-04 01:33:49 (4281) [INFO] 
* 2024-01-04 01:33:49 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-04 01:33:49 (4251) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-04 01:34:01 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-04 01:34:01 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-04 01:34:01 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-04 01:34:01 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-04 01:34:01 (4264) [INFO] Trying other mirror.
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-04 01:34:01 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-04 01:34:01 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-04 01:34:01 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-04 01:34:01 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-04 01:34:01 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-04 01:34:01 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-04 01:34:01 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-04 01:34:01 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-04 01:34:01 (4264) [INFO]         or
* 2024-01-04 01:34:01 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-04 01:34:01 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-04 01:34:01 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-04 01:34:01 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-04 01:34:01 (4264) [INFO]         compromise:
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-04 01:34:01 (4264) [INFO] 
* 2024-01-04 01:34:01 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-04 01:34:02 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-04 01:34:02 (4281) [INFO] 
* 2024-01-04 01:34:02 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-04 01:34:02 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-04 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-04 01:34:04 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-04 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-04 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-04 01:34:04 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-04 01:34:04 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-04 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-04 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-04 01:34:04 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-04 01:34:04 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-04 01:34:11 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-04 01:34:11 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-04 01:34:11 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-04 01:34:11 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-04 01:34:11 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-04 01:34:11 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-04 01:34:11 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fNNFTlYe9r/ea_profile.json
* 2024-01-04 01:34:17 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fNNFTlYe9r/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-04 01:34:17 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-05 01:34:26 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-05 01:34:27 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-05 01:34:27 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-05 01:34:27 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-05 01:34:27 (4251) [INFO] 
* 2024-01-05 01:34:27 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-05 01:34:27 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-05 01:34:27 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-05 01:34:27 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-05 01:34:27 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-05 01:34:27 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-05 01:34:27 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-05 01:34:27 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-05 01:34:27 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-05 01:34:27 (4281) [INFO] 
* 2024-01-05 01:34:27 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-05 01:34:27 (4251) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-05 01:34:48 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-05 01:34:48 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-05 01:34:48 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-05 01:34:48 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-05 01:34:48 (4264) [INFO] Trying other mirror.
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-05 01:34:48 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-05 01:34:48 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-05 01:34:48 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-05 01:34:48 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-05 01:34:48 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-05 01:34:48 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-05 01:34:48 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-05 01:34:48 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-05 01:34:48 (4264) [INFO]         or
* 2024-01-05 01:34:48 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-05 01:34:48 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-05 01:34:48 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-05 01:34:48 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-05 01:34:48 (4264) [INFO]         compromise:
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-05 01:34:48 (4264) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-05 01:34:48 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-05 01:34:48 (4281) [INFO] 
* 2024-01-05 01:34:48 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-05 01:34:48 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-05 01:34:48 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-05 01:34:50 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-05 01:34:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-05 01:34:50 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-05 01:34:50 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-05 01:34:50 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-05 01:34:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-05 01:34:50 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-05 01:34:50 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-05 01:34:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-05 01:34:55 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-05 01:34:55 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-05 01:34:55 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-05 01:34:55 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-05 01:34:55 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-05 01:34:55 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-05 01:34:55 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jGAqtPVJjk/ea_profile.json
* 2024-01-05 01:35:02 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jGAqtPVJjk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-05 01:35:02 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-06 01:35:38 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-06 01:35:39 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-06 01:35:39 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-06 01:35:39 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-06 01:35:39 (4251) [INFO] 
* 2024-01-06 01:35:39 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-06 01:35:39 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-06 01:35:39 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-06 01:35:39 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-06 01:35:39 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-06 01:35:39 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-06 01:35:39 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-06 01:35:39 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-06 01:35:39 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-06 01:35:39 (4281) [INFO] 
* 2024-01-06 01:35:39 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-06 01:35:39 (4251) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-06 01:35:48 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-06 01:35:48 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-06 01:35:48 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-06 01:35:48 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-06 01:35:48 (4264) [INFO] Trying other mirror.
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-06 01:35:48 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-06 01:35:48 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-06 01:35:48 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-06 01:35:48 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-06 01:35:48 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-06 01:35:48 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-06 01:35:48 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-06 01:35:48 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-06 01:35:48 (4264) [INFO]         or
* 2024-01-06 01:35:48 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-06 01:35:48 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-06 01:35:48 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-06 01:35:48 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-06 01:35:48 (4264) [INFO]         compromise:
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-06 01:35:48 (4264) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-06 01:35:48 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-06 01:35:48 (4281) [INFO] 
* 2024-01-06 01:35:48 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-06 01:35:48 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-06 01:35:48 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-06 01:35:50 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-06 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-06 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-06 01:35:50 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-06 01:35:50 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-06 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-06 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-06 01:35:50 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-06 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-06 01:35:55 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-06 01:35:55 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-06 01:35:55 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-06 01:35:56 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-06 01:35:56 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-06 01:35:56 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-06 01:35:56 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qZeIH01XbF/ea_profile.json
* 2024-01-06 01:36:02 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qZeIH01XbF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-06 01:36:02 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-07 01:35:36 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-07 01:35:37 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-07 01:35:37 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-07 01:35:37 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-07 01:35:37 (4251) [INFO] 
* 2024-01-07 01:35:37 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-07 01:35:37 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-07 01:35:37 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-07 01:35:37 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-07 01:35:37 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-07 01:35:37 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-07 01:35:37 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-07 01:35:37 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-07 01:35:37 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-07 01:35:37 (4281) [INFO] 
* 2024-01-07 01:35:37 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-07 01:35:37 (4251) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-07 01:35:51 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-07 01:35:51 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-07 01:35:51 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-07 01:35:51 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-07 01:35:51 (4264) [INFO] Trying other mirror.
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-07 01:35:51 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-07 01:35:51 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-07 01:35:51 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-07 01:35:51 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-07 01:35:51 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-07 01:35:51 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-07 01:35:51 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-07 01:35:51 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-07 01:35:51 (4264) [INFO]         or
* 2024-01-07 01:35:51 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-07 01:35:51 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-07 01:35:51 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-07 01:35:51 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-07 01:35:51 (4264) [INFO]         compromise:
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-07 01:35:51 (4264) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-07 01:35:51 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-07 01:35:51 (4281) [INFO] 
* 2024-01-07 01:35:51 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-07 01:35:51 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-07 01:35:51 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-07 01:35:53 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-07 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-07 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-07 01:35:53 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-07 01:35:53 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-07 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-07 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-07 01:35:53 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-07 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-07 01:36:02 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-07 01:36:02 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-07 01:36:02 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-07 01:36:02 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-07 01:36:02 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-07 01:36:03 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-07 01:36:03 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nRvEevb8L_/ea_profile.json
* 2024-01-07 01:36:10 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nRvEevb8L_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-07 01:36:10 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-08 01:34:06 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-08 01:34:07 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-08 01:34:07 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-08 01:34:07 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-08 01:34:07 (4251) [INFO] 
* 2024-01-08 01:34:07 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-08 01:34:08 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-08 01:34:08 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-08 01:34:08 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-08 01:34:08 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-08 01:34:08 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-08 01:34:08 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-08 01:34:08 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-08 01:34:08 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-08 01:34:08 (4281) [INFO] 
* 2024-01-08 01:34:08 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-08 01:34:08 (4251) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-08 01:34:22 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-08 01:34:22 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-08 01:34:22 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-08 01:34:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-08 01:34:22 (4264) [INFO] Trying other mirror.
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-08 01:34:22 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-08 01:34:22 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-08 01:34:22 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-08 01:34:22 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-08 01:34:22 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-08 01:34:22 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-08 01:34:22 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-08 01:34:22 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-08 01:34:22 (4264) [INFO]         or
* 2024-01-08 01:34:22 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-08 01:34:22 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-08 01:34:22 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-08 01:34:22 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-08 01:34:22 (4264) [INFO]         compromise:
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-08 01:34:22 (4264) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-08 01:34:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-08 01:34:22 (4281) [INFO] 
* 2024-01-08 01:34:22 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-08 01:34:22 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-08 01:34:22 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-08 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-08 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-08 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-08 01:34:24 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-08 01:34:24 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-08 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-08 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-08 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-08 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-08 01:34:30 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-08 01:34:30 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-08 01:34:30 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-08 01:34:30 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-08 01:34:30 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-08 01:34:30 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-08 01:34:30 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MjRs36FCxS/ea_profile.json
* 2024-01-08 01:34:36 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MjRs36FCxS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-08 01:34:36 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-09 01:34:07 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-09 01:34:08 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-09 01:34:08 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-09 01:34:08 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-09 01:34:08 (4251) [INFO] 
* 2024-01-09 01:34:08 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-09 01:34:09 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-09 01:34:09 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-09 01:34:09 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-09 01:34:09 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-09 01:34:09 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-09 01:34:09 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-09 01:34:09 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-09 01:34:09 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-09 01:34:09 (4281) [INFO] 
* 2024-01-09 01:34:09 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-09 01:34:09 (4251) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-09 01:34:22 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-09 01:34:22 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-09 01:34:22 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-09 01:34:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-09 01:34:22 (4264) [INFO] Trying other mirror.
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-09 01:34:22 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-09 01:34:22 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-09 01:34:22 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-09 01:34:22 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-09 01:34:22 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-09 01:34:22 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-09 01:34:22 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-09 01:34:22 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-09 01:34:22 (4264) [INFO]         or
* 2024-01-09 01:34:22 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-09 01:34:22 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-09 01:34:22 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-09 01:34:22 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-09 01:34:22 (4264) [INFO]         compromise:
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-09 01:34:22 (4264) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-09 01:34:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-09 01:34:22 (4281) [INFO] 
* 2024-01-09 01:34:22 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-09 01:34:22 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-09 01:34:22 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-09 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-09 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-09 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-09 01:34:24 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-09 01:34:24 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-09 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-09 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-09 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-09 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-09 01:34:28 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-09 01:34:28 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-09 01:34:28 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-09 01:34:28 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-09 01:34:28 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-09 01:34:28 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-09 01:34:28 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1X6awwF3Pq/ea_profile.json
* 2024-01-09 01:34:34 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1X6awwF3Pq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-09 01:34:34 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-10 01:34:10 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-10 01:34:11 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-10 01:34:11 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-10 01:34:11 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-10 01:34:11 (4251) [INFO] 
* 2024-01-10 01:34:11 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-10 01:34:11 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-10 01:34:11 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-10 01:34:11 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-10 01:34:11 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-10 01:34:11 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-10 01:34:11 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-10 01:34:11 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-10 01:34:11 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-10 01:34:11 (4281) [INFO] 
* 2024-01-10 01:34:11 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-10 01:34:11 (4251) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-10 01:34:23 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-10 01:34:23 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-10 01:34:23 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-10 01:34:23 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-10 01:34:23 (4264) [INFO] Trying other mirror.
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-10 01:34:23 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-10 01:34:23 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-10 01:34:23 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-10 01:34:23 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-10 01:34:23 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-10 01:34:23 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-10 01:34:23 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-10 01:34:23 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-10 01:34:23 (4264) [INFO]         or
* 2024-01-10 01:34:23 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-10 01:34:23 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-10 01:34:23 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-10 01:34:23 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-10 01:34:23 (4264) [INFO]         compromise:
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-10 01:34:23 (4264) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-10 01:34:23 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-10 01:34:23 (4281) [INFO] 
* 2024-01-10 01:34:23 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-10 01:34:23 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-10 01:34:23 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-10 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-10 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-10 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-10 01:34:24 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-10 01:34:24 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-10 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-10 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-10 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-10 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-10 01:34:28 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-10 01:34:28 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-10 01:34:28 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-10 01:34:28 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-10 01:34:28 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-10 01:34:29 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-10 01:34:29 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TVJPh31yul/ea_profile.json
* 2024-01-10 01:34:36 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TVJPh31yul/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-10 01:34:36 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-11 01:33:44 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-11 01:33:45 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-11 01:33:45 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-11 01:33:45 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-11 01:33:45 (4251) [INFO] 
* 2024-01-11 01:33:45 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-11 01:33:45 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-11 01:33:45 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-11 01:33:45 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-11 01:33:45 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-11 01:33:45 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-11 01:33:45 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-11 01:33:45 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-11 01:33:45 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-11 01:33:45 (4281) [INFO] 
* 2024-01-11 01:33:45 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-11 01:33:45 (4251) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-11 01:34:07 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-11 01:34:07 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-11 01:34:07 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-11 01:34:07 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-11 01:34:07 (4264) [INFO] Trying other mirror.
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-11 01:34:07 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-11 01:34:07 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-11 01:34:07 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-11 01:34:07 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-11 01:34:07 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-11 01:34:07 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-11 01:34:07 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-11 01:34:07 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-11 01:34:07 (4264) [INFO]         or
* 2024-01-11 01:34:07 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-11 01:34:07 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-11 01:34:07 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-11 01:34:07 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-11 01:34:07 (4264) [INFO]         compromise:
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-11 01:34:07 (4264) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-11 01:34:07 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-11 01:34:07 (4281) [INFO] 
* 2024-01-11 01:34:07 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-11 01:34:07 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-11 01:34:07 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-11 01:34:09 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-11 01:34:09 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-11 01:34:09 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-11 01:34:09 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-11 01:34:09 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-11 01:34:09 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-11 01:34:09 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-11 01:34:09 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-11 01:34:09 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-11 01:34:19 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-11 01:34:19 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-11 01:34:19 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-11 01:34:19 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-11 01:34:19 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-11 01:34:19 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-11 01:34:19 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jPM26KzylD/ea_profile.json
* 2024-01-11 01:34:26 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jPM26KzylD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-11 01:34:26 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-12 01:33:56 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-12 01:33:57 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-12 01:33:57 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-12 01:33:57 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-12 01:33:57 (4251) [INFO] 
* 2024-01-12 01:33:57 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-12 01:33:57 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-12 01:33:57 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-12 01:33:57 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-12 01:33:57 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-12 01:33:57 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-12 01:33:57 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-12 01:33:57 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-12 01:33:57 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-12 01:33:57 (4281) [INFO] 
* 2024-01-12 01:33:57 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-12 01:33:57 (4251) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-12 01:34:17 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-12 01:34:17 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-12 01:34:17 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-12 01:34:17 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-12 01:34:17 (4264) [INFO] Trying other mirror.
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-12 01:34:17 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-12 01:34:17 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-12 01:34:17 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-12 01:34:17 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-12 01:34:17 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-12 01:34:17 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-12 01:34:17 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-12 01:34:17 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-12 01:34:17 (4264) [INFO]         or
* 2024-01-12 01:34:17 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-12 01:34:17 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-12 01:34:17 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-12 01:34:17 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-12 01:34:17 (4264) [INFO]         compromise:
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-12 01:34:17 (4264) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-12 01:34:17 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-12 01:34:17 (4281) [INFO] 
* 2024-01-12 01:34:17 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-12 01:34:17 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-12 01:34:17 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-12 01:34:18 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-12 01:34:18 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-12 01:34:18 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-12 01:34:18 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-12 01:34:18 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-12 01:34:18 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-12 01:34:18 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-12 01:34:18 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-12 01:34:18 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-12 01:34:22 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-12 01:34:22 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-12 01:34:22 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-12 01:34:22 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-12 01:34:22 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-12 01:34:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-12 01:34:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2Vy1STxhQW/ea_profile.json
* 2024-01-12 01:34:26 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2Vy1STxhQW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-12 01:34:26 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-13 01:35:36 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-13 01:35:36 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-13 01:35:36 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-13 01:35:36 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-13 01:35:36 (4251) [INFO] 
* 2024-01-13 01:35:36 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-13 01:35:36 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-13 01:35:36 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-13 01:35:36 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-13 01:35:36 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-13 01:35:36 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-13 01:35:36 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-13 01:35:36 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-13 01:35:37 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-13 01:35:37 (4281) [INFO] 
* 2024-01-13 01:35:37 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-13 01:35:37 (4251) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-13 01:35:49 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-13 01:35:49 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-13 01:35:49 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-13 01:35:49 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-13 01:35:49 (4264) [INFO] Trying other mirror.
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-13 01:35:49 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-13 01:35:49 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-13 01:35:49 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-13 01:35:49 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-13 01:35:49 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-13 01:35:49 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-13 01:35:49 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-13 01:35:49 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-13 01:35:49 (4264) [INFO]         or
* 2024-01-13 01:35:49 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-13 01:35:49 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-13 01:35:49 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-13 01:35:49 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-13 01:35:49 (4264) [INFO]         compromise:
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-13 01:35:49 (4264) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-13 01:35:49 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-13 01:35:49 (4281) [INFO] 
* 2024-01-13 01:35:49 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-13 01:35:49 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-13 01:35:49 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-13 01:35:50 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-13 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-13 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-13 01:35:50 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-13 01:35:50 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-13 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-13 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-13 01:35:50 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-13 01:35:50 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-13 01:35:55 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-13 01:35:55 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-13 01:35:55 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-13 01:35:55 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-13 01:35:55 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-13 01:35:55 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-13 01:35:55 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UHVXyWUJJx/ea_profile.json
* 2024-01-13 01:36:01 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UHVXyWUJJx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-13 01:36:01 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-14 01:35:02 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-14 01:35:03 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-14 01:35:03 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-14 01:35:03 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-14 01:35:03 (4251) [INFO] 
* 2024-01-14 01:35:03 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-14 01:35:04 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-14 01:35:04 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-14 01:35:04 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-14 01:35:04 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-14 01:35:04 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-14 01:35:04 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-14 01:35:04 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-14 01:35:04 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-14 01:35:04 (4281) [INFO] 
* 2024-01-14 01:35:04 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-14 01:35:04 (4251) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-14 01:35:15 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-14 01:35:15 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-14 01:35:15 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-14 01:35:15 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-14 01:35:15 (4264) [INFO] Trying other mirror.
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-14 01:35:15 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-14 01:35:15 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-14 01:35:15 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-14 01:35:15 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-14 01:35:15 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-14 01:35:15 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-14 01:35:15 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-14 01:35:15 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-14 01:35:15 (4264) [INFO]         or
* 2024-01-14 01:35:15 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-14 01:35:15 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-14 01:35:15 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-14 01:35:15 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-14 01:35:15 (4264) [INFO]         compromise:
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-14 01:35:15 (4264) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-14 01:35:15 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-14 01:35:15 (4281) [INFO] 
* 2024-01-14 01:35:15 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-14 01:35:15 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-14 01:35:15 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-14 01:35:17 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-14 01:35:17 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-14 01:35:17 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-14 01:35:17 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-14 01:35:17 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-14 01:35:17 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-14 01:35:17 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-14 01:35:17 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-14 01:35:17 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-14 01:35:23 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-14 01:35:23 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-14 01:35:23 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-14 01:35:23 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-14 01:35:23 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-14 01:35:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-14 01:35:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9445tSRTwd/ea_profile.json
* 2024-01-14 01:35:28 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9445tSRTwd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-14 01:35:28 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-15 01:36:54 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-15 01:36:54 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-15 01:36:55 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-15 01:36:55 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-15 01:36:55 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-15 01:36:55 (4251) [INFO] 
* 2024-01-15 01:36:55 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-15 01:36:55 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-15 01:36:55 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-15 01:36:55 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-15 01:36:55 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-15 01:36:55 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-15 01:36:55 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-15 01:36:55 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-15 01:36:55 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-15 01:36:55 (4281) [INFO] 
* 2024-01-15 01:36:55 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-15 01:36:55 (4251) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-15 01:37:09 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-15 01:37:09 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-15 01:37:09 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-15 01:37:09 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-15 01:37:09 (4264) [INFO] Trying other mirror.
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-15 01:37:09 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-15 01:37:09 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-15 01:37:09 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-15 01:37:09 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-15 01:37:09 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-15 01:37:09 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-15 01:37:09 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-15 01:37:09 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-15 01:37:09 (4264) [INFO]         or
* 2024-01-15 01:37:09 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-15 01:37:09 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-15 01:37:09 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-15 01:37:09 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-15 01:37:09 (4264) [INFO]         compromise:
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-15 01:37:09 (4264) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-15 01:37:09 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-15 01:37:09 (4281) [INFO] 
* 2024-01-15 01:37:09 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-15 01:37:09 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-15 01:37:09 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-15 01:37:11 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-15 01:37:11 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-15 01:37:11 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-15 01:37:11 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-15 01:37:11 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-15 01:37:11 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-15 01:37:11 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-15 01:37:11 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-15 01:37:11 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-15 01:37:16 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-15 01:37:16 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-15 01:37:16 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-15 01:37:16 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-15 01:37:16 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-15 01:37:16 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-15 01:37:17 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PcLmI_CK58/ea_profile.json
* 2024-01-15 01:37:25 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PcLmI_CK58/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-15 01:37:25 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-16 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-16 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-16 01:34:04 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-16 01:34:04 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-16 01:34:04 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-16 01:34:04 (4251) [INFO] 
* 2024-01-16 01:34:04 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-16 01:34:04 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-16 01:34:04 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-16 01:34:04 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-16 01:34:04 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-16 01:34:04 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-16 01:34:04 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-16 01:34:04 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-16 01:34:04 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-16 01:34:04 (4281) [INFO] 
* 2024-01-16 01:34:04 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-16 01:34:04 (4251) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-16 01:34:22 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-16 01:34:22 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-16 01:34:22 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-16 01:34:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-16 01:34:22 (4264) [INFO] Trying other mirror.
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-16 01:34:22 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-16 01:34:22 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-16 01:34:22 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-16 01:34:22 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-16 01:34:22 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-16 01:34:22 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-16 01:34:22 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-16 01:34:22 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-16 01:34:22 (4264) [INFO]         or
* 2024-01-16 01:34:22 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-16 01:34:22 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-16 01:34:22 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-16 01:34:22 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-16 01:34:22 (4264) [INFO]         compromise:
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-16 01:34:22 (4264) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-16 01:34:22 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-16 01:34:22 (4281) [INFO] 
* 2024-01-16 01:34:22 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-16 01:34:22 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-16 01:34:22 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-16 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-16 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-16 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-16 01:34:24 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-16 01:34:24 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-16 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-16 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-16 01:34:24 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-16 01:34:24 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-16 01:34:30 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-16 01:34:30 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-16 01:34:30 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-16 01:34:30 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-16 01:34:30 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-16 01:34:30 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-16 01:34:31 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NPHcZ4mBnS/ea_profile.json
* 2024-01-16 01:34:37 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NPHcZ4mBnS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-16 01:34:37 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-17 01:36:03 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-17 01:36:03 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-17 01:36:03 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-17 01:36:04 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-17 01:36:04 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-17 01:36:04 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-17 01:36:04 (4251) [INFO] 
* 2024-01-17 01:36:04 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-17 01:36:05 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 974797.
* 2024-01-17 01:36:05 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:05 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:05 (4264) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-17 01:36:05 (4264) [INFO]     Started: Wed Jan 17 01:35:58 2024 - 00:07 ago
* 2024-01-17 01:36:05 (4264) [INFO]     State  : Sleeping, pid: 974797
* 2024-01-17 01:36:07 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:07 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:07 (4264) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-17 01:36:07 (4264) [INFO]     Started: Wed Jan 17 01:35:58 2024 - 00:09 ago
* 2024-01-17 01:36:07 (4264) [INFO]     State  : Sleeping, pid: 974797
* 2024-01-17 01:36:09 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:09 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:09 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-17 01:36:09 (4264) [INFO]     Started: Wed Jan 17 01:35:58 2024 - 00:11 ago
* 2024-01-17 01:36:09 (4264) [INFO]     State  : Sleeping, pid: 974797
* 2024-01-17 01:36:11 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:11 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:11 (4264) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-01-17 01:36:11 (4264) [INFO]     Started: Wed Jan 17 01:35:58 2024 - 00:13 ago
* 2024-01-17 01:36:11 (4264) [INFO]     State  : Sleeping, pid: 974797
* 2024-01-17 01:36:13 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:13 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:13 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-17 01:36:13 (4264) [INFO]     Started: Wed Jan 17 01:35:58 2024 - 00:15 ago
* 2024-01-17 01:36:13 (4264) [INFO]     State  : Sleeping, pid: 974797
* 2024-01-17 01:36:15 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:15 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:15 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-17 01:36:15 (4264) [INFO]     Started: Wed Jan 17 01:35:58 2024 - 00:17 ago
* 2024-01-17 01:36:15 (4264) [INFO]     State  : Sleeping, pid: 974797
* 2024-01-17 01:36:17 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 975428.
* 2024-01-17 01:36:17 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:17 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:17 (4264) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-01-17 01:36:17 (4264) [INFO]     Started: Wed Jan 17 01:36:14 2024 - 00:03 ago
* 2024-01-17 01:36:17 (4264) [INFO]     State  : Sleeping, pid: 975428
* 2024-01-17 01:36:19 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 01:36:19 (4264) [INFO]   The other application is: yum
* 2024-01-17 01:36:19 (4264) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-01-17 01:36:19 (4264) [INFO]     Started: Wed Jan 17 01:36:14 2024 - 00:05 ago
* 2024-01-17 01:36:19 (4264) [INFO]     State  : Sleeping, pid: 975428
* 2024-01-17 01:36:21 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-17 01:36:21 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-17 01:36:21 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-17 01:36:21 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-17 01:36:21 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-17 01:36:21 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-17 01:36:21 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-17 01:36:21 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-17 01:36:21 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-17 01:36:21 (4281) [INFO] 
* 2024-01-17 01:36:21 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-17 01:36:21 (4251) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-17 01:36:29 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-17 01:36:29 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-17 01:36:29 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-17 01:36:29 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-17 01:36:29 (4264) [INFO] Trying other mirror.
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-17 01:36:29 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-17 01:36:29 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-17 01:36:29 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-17 01:36:29 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-17 01:36:29 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-17 01:36:29 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-17 01:36:29 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-17 01:36:29 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-17 01:36:29 (4264) [INFO]         or
* 2024-01-17 01:36:29 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-17 01:36:29 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-17 01:36:29 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-17 01:36:29 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-17 01:36:29 (4264) [INFO]         compromise:
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-17 01:36:29 (4264) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-17 01:36:29 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-17 01:36:29 (4281) [INFO] 
* 2024-01-17 01:36:29 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-17 01:36:29 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-17 01:36:29 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-17 01:36:31 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-17 01:36:31 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-17 01:36:31 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-17 01:36:31 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-17 01:36:31 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-17 01:36:31 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-17 01:36:31 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-17 01:36:31 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-17 01:36:31 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-17 01:36:34 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-17 01:36:34 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-17 01:36:34 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-17 01:36:34 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-17 01:36:34 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-17 01:36:35 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-17 01:36:35 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ITGMv99y4J/ea_profile.json
* 2024-01-17 01:36:41 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ITGMv99y4J/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-17 01:36:41 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-18 01:34:05 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-18 01:34:05 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-18 01:34:05 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-18 01:34:06 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-18 01:34:06 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-18 01:34:06 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-18 01:34:06 (4251) [INFO] 
* 2024-01-18 01:34:06 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-18 01:34:06 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 798261.
* 2024-01-18 01:34:06 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-18 01:34:06 (4264) [INFO]   The other application is: yum
* 2024-01-18 01:34:06 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-18 01:34:06 (4264) [INFO]     Started: Thu Jan 18 01:33:59 2024 - 00:07 ago
* 2024-01-18 01:34:06 (4264) [INFO]     State  : Sleeping, pid: 798261
* 2024-01-18 01:34:08 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-18 01:34:08 (4264) [INFO]   The other application is: yum
* 2024-01-18 01:34:08 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-18 01:34:08 (4264) [INFO]     Started: Thu Jan 18 01:33:59 2024 - 00:09 ago
* 2024-01-18 01:34:08 (4264) [INFO]     State  : Sleeping, pid: 798261
* 2024-01-18 01:34:10 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-18 01:34:10 (4264) [INFO]   The other application is: yum
* 2024-01-18 01:34:10 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-18 01:34:10 (4264) [INFO]     Started: Thu Jan 18 01:33:59 2024 - 00:11 ago
* 2024-01-18 01:34:10 (4264) [INFO]     State  : Sleeping, pid: 798261
* 2024-01-18 01:34:12 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-18 01:34:12 (4264) [INFO]   The other application is: yum
* 2024-01-18 01:34:12 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-18 01:34:12 (4264) [INFO]     Started: Thu Jan 18 01:33:59 2024 - 00:13 ago
* 2024-01-18 01:34:12 (4264) [INFO]     State  : Sleeping, pid: 798261
* 2024-01-18 01:34:14 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-18 01:34:14 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-18 01:34:14 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-18 01:34:14 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-18 01:34:14 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-18 01:34:14 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-18 01:34:14 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-18 01:34:14 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-18 01:34:14 (4264) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-01-18 01:34:14 (4281) [INFO] 
* 2024-01-18 01:34:14 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-18 01:34:14 (4251) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-18 01:34:21 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-18 01:34:21 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-18 01:34:21 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-18 01:34:21 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-18 01:34:21 (4264) [INFO] Trying other mirror.
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-18 01:34:21 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-18 01:34:21 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-18 01:34:21 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-18 01:34:21 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-18 01:34:21 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-18 01:34:21 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-18 01:34:21 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-18 01:34:21 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-18 01:34:21 (4264) [INFO]         or
* 2024-01-18 01:34:21 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-18 01:34:21 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-18 01:34:21 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-18 01:34:21 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-18 01:34:21 (4264) [INFO]         compromise:
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-18 01:34:21 (4264) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-18 01:34:21 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-18 01:34:21 (4281) [INFO] 
* 2024-01-18 01:34:21 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-18 01:34:21 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-18 01:34:21 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-18 01:34:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-18 01:34:23 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-18 01:34:23 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-18 01:34:23 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-18 01:34:23 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-18 01:34:23 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-18 01:34:23 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-18 01:34:23 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-18 01:34:23 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-18 01:34:27 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-18 01:34:27 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-18 01:34:27 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-18 01:34:27 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-18 01:34:27 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-18 01:34:27 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-18 01:34:27 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iENCIgoDOv/ea_profile.json
* 2024-01-18 01:34:31 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iENCIgoDOv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-18 01:34:31 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-19 01:34:39 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-19 01:34:40 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-19 01:34:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-19 01:34:40 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-19 01:34:40 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-19 01:34:40 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-19 01:34:40 (4251) [INFO] 
* 2024-01-19 01:34:41 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-19 01:34:41 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 657920.
* 2024-01-19 01:34:41 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-19 01:34:41 (4264) [INFO]   The other application is: yum
* 2024-01-19 01:34:41 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-19 01:34:41 (4264) [INFO]     Started: Fri Jan 19 01:34:36 2024 - 00:05 ago
* 2024-01-19 01:34:41 (4264) [INFO]     State  : Sleeping, pid: 657920
* 2024-01-19 01:34:43 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-19 01:34:43 (4264) [INFO]   The other application is: yum
* 2024-01-19 01:34:43 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-19 01:34:43 (4264) [INFO]     Started: Fri Jan 19 01:34:36 2024 - 00:07 ago
* 2024-01-19 01:34:43 (4264) [INFO]     State  : Sleeping, pid: 657920
* 2024-01-19 01:34:45 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-19 01:34:45 (4264) [INFO]   The other application is: yum
* 2024-01-19 01:34:45 (4264) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-19 01:34:45 (4264) [INFO]     Started: Fri Jan 19 01:34:36 2024 - 00:09 ago
* 2024-01-19 01:34:45 (4264) [INFO]     State  : Sleeping, pid: 657920
* 2024-01-19 01:34:47 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-19 01:34:47 (4264) [INFO]   The other application is: yum
* 2024-01-19 01:34:47 (4264) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-01-19 01:34:47 (4264) [INFO]     Started: Fri Jan 19 01:34:36 2024 - 00:11 ago
* 2024-01-19 01:34:47 (4264) [INFO]     State  : Sleeping, pid: 657920
* 2024-01-19 01:34:49 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-19 01:34:49 (4264) [INFO]   The other application is: yum
* 2024-01-19 01:34:49 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-19 01:34:49 (4264) [INFO]     Started: Fri Jan 19 01:34:36 2024 - 00:13 ago
* 2024-01-19 01:34:49 (4264) [INFO]     State  : Sleeping, pid: 657920
* 2024-01-19 01:34:51 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-19 01:34:51 (4264) [INFO]   The other application is: yum
* 2024-01-19 01:34:51 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-19 01:34:51 (4264) [INFO]     Started: Fri Jan 19 01:34:36 2024 - 00:15 ago
* 2024-01-19 01:34:51 (4264) [INFO]     State  : Sleeping, pid: 657920
* 2024-01-19 01:34:53 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-19 01:34:53 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-19 01:34:53 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-19 01:34:53 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-19 01:34:53 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-19 01:34:53 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-19 01:34:53 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-19 01:34:53 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-19 01:34:53 (4264) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-01-19 01:34:53 (4281) [INFO] 
* 2024-01-19 01:34:53 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-19 01:34:53 (4251) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-19 01:34:59 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-19 01:34:59 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-19 01:34:59 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-19 01:34:59 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-19 01:34:59 (4264) [INFO] Trying other mirror.
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-19 01:34:59 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-19 01:34:59 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-19 01:34:59 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-19 01:34:59 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-19 01:34:59 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-19 01:34:59 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-19 01:34:59 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-19 01:34:59 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-19 01:34:59 (4264) [INFO]         or
* 2024-01-19 01:34:59 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-19 01:34:59 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-19 01:34:59 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-19 01:34:59 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-19 01:34:59 (4264) [INFO]         compromise:
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-19 01:34:59 (4264) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-19 01:34:59 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-19 01:34:59 (4281) [INFO] 
* 2024-01-19 01:34:59 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-19 01:34:59 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-19 01:34:59 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-19 01:35:02 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-19 01:35:02 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-19 01:35:02 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-19 01:35:02 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-19 01:35:02 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-19 01:35:02 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-19 01:35:02 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-19 01:35:02 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-19 01:35:02 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-19 01:35:10 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-19 01:35:10 (1634) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 659160.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (325 MB VSZ)
    Started: Fri Jan 19 01:34:53 2024 - 00:09 ago
    State  : Sleeping, pid: 659160
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Fri Jan 19 01:34:53 2024 - 00:11 ago
    State  : Sleeping, pid: 659160
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Fri Jan 19 01:34:53 2024 - 00:13 ago
    State  : Sleeping, pid: 659160
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-19 01:35:10 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-19 01:35:10 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-19 01:35:10 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-19 01:35:11 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-19 01:35:11 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tY9tmyT0zG/ea_profile.json
* 2024-01-19 01:35:14 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tY9tmyT0zG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-19 01:35:14 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-20 01:35:27 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-20 01:35:27 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-20 01:35:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-20 01:35:28 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-20 01:35:29 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-20 01:35:29 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-20 01:35:29 (4251) [INFO] 
* 2024-01-20 01:35:29 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-20 01:35:29 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 474675.
* 2024-01-20 01:35:29 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-20 01:35:29 (4264) [INFO]   The other application is: yum
* 2024-01-20 01:35:29 (4264) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-20 01:35:29 (4264) [INFO]     Started: Sat Jan 20 01:35:25 2024 - 00:04 ago
* 2024-01-20 01:35:29 (4264) [INFO]     State  : Sleeping, pid: 474675
* 2024-01-20 01:35:31 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-20 01:35:31 (4264) [INFO]   The other application is: yum
* 2024-01-20 01:35:31 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-20 01:35:31 (4264) [INFO]     Started: Sat Jan 20 01:35:25 2024 - 00:06 ago
* 2024-01-20 01:35:31 (4264) [INFO]     State  : Sleeping, pid: 474675
* 2024-01-20 01:35:33 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-20 01:35:33 (4264) [INFO]   The other application is: yum
* 2024-01-20 01:35:33 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-20 01:35:33 (4264) [INFO]     Started: Sat Jan 20 01:35:25 2024 - 00:08 ago
* 2024-01-20 01:35:33 (4264) [INFO]     State  : Sleeping, pid: 474675
* 2024-01-20 01:35:35 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-20 01:35:35 (4264) [INFO]   The other application is: yum
* 2024-01-20 01:35:35 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-20 01:35:35 (4264) [INFO]     Started: Sat Jan 20 01:35:25 2024 - 00:10 ago
* 2024-01-20 01:35:35 (4264) [INFO]     State  : Sleeping, pid: 474675
* 2024-01-20 01:35:37 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-20 01:35:37 (4264) [INFO]   The other application is: yum
* 2024-01-20 01:35:37 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-20 01:35:37 (4264) [INFO]     Started: Sat Jan 20 01:35:25 2024 - 00:12 ago
* 2024-01-20 01:35:37 (4264) [INFO]     State  : Sleeping, pid: 474675
* 2024-01-20 01:35:39 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 475279.
* 2024-01-20 01:35:39 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-20 01:35:39 (4264) [INFO]   The other application is: yum
* 2024-01-20 01:35:39 (4264) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-01-20 01:35:39 (4264) [INFO]     Started: Sat Jan 20 01:35:37 2024 - 00:02 ago
* 2024-01-20 01:35:39 (4264) [INFO]     State  : Sleeping, pid: 475279
* 2024-01-20 01:35:41 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-20 01:35:41 (4264) [INFO]   The other application is: yum
* 2024-01-20 01:35:41 (4264) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-01-20 01:35:41 (4264) [INFO]     Started: Sat Jan 20 01:35:37 2024 - 00:04 ago
* 2024-01-20 01:35:41 (4264) [INFO]     State  : Uninterruptible, pid: 475279
* 2024-01-20 01:35:43 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-20 01:35:43 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-20 01:35:43 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-20 01:35:43 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-20 01:35:43 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-20 01:35:43 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-20 01:35:43 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-20 01:35:43 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-20 01:35:43 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-20 01:35:43 (4281) [INFO] 
* 2024-01-20 01:35:43 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-20 01:35:43 (4251) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-20 01:35:50 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-20 01:35:50 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-20 01:35:50 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-20 01:35:50 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-20 01:35:50 (4264) [INFO] Trying other mirror.
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-20 01:35:50 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-20 01:35:50 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-20 01:35:50 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-20 01:35:50 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-20 01:35:50 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-20 01:35:50 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-20 01:35:50 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-20 01:35:50 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-20 01:35:50 (4264) [INFO]         or
* 2024-01-20 01:35:50 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-20 01:35:50 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-20 01:35:50 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-20 01:35:50 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-20 01:35:50 (4264) [INFO]         compromise:
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-20 01:35:50 (4264) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-20 01:35:50 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-20 01:35:50 (4281) [INFO] 
* 2024-01-20 01:35:50 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-20 01:35:50 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-20 01:35:50 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-20 01:35:53 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-20 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-20 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-20 01:35:53 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-20 01:35:53 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-20 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-20 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-20 01:35:53 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-20 01:35:53 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-20 01:35:57 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-20 01:35:57 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-20 01:35:57 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-20 01:35:57 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-20 01:35:57 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-20 01:35:58 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-20 01:35:58 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6Dci8R0HZ_/ea_profile.json
* 2024-01-20 01:36:05 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6Dci8R0HZ_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-20 01:36:05 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-21 01:36:11 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-21 01:36:12 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-21 01:36:12 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-21 01:36:12 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-21 01:36:12 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-21 01:36:12 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-21 01:36:12 (4251) [INFO] 
* 2024-01-21 01:36:12 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-21 01:36:12 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 924945.
* 2024-01-21 01:36:12 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-21 01:36:12 (4264) [INFO]   The other application is: yum
* 2024-01-21 01:36:12 (4264) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-21 01:36:12 (4264) [INFO]     Started: Sun Jan 21 01:36:09 2024 - 00:03 ago
* 2024-01-21 01:36:12 (4264) [INFO]     State  : Sleeping, pid: 924945
* 2024-01-21 01:36:14 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-21 01:36:14 (4264) [INFO]   The other application is: yum
* 2024-01-21 01:36:14 (4264) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-21 01:36:14 (4264) [INFO]     Started: Sun Jan 21 01:36:09 2024 - 00:05 ago
* 2024-01-21 01:36:14 (4264) [INFO]     State  : Sleeping, pid: 924945
* 2024-01-21 01:36:17 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-21 01:36:17 (4264) [INFO]   The other application is: yum
* 2024-01-21 01:36:17 (4264) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-21 01:36:17 (4264) [INFO]     Started: Sun Jan 21 01:36:09 2024 - 00:08 ago
* 2024-01-21 01:36:17 (4264) [INFO]     State  : Sleeping, pid: 924945
* 2024-01-21 01:36:19 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-21 01:36:19 (4264) [INFO]   The other application is: yum
* 2024-01-21 01:36:19 (4264) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-01-21 01:36:19 (4264) [INFO]     Started: Sun Jan 21 01:36:09 2024 - 00:10 ago
* 2024-01-21 01:36:19 (4264) [INFO]     State  : Sleeping, pid: 924945
* 2024-01-21 01:36:21 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-21 01:36:21 (4264) [INFO]   The other application is: yum
* 2024-01-21 01:36:21 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-21 01:36:21 (4264) [INFO]     Started: Sun Jan 21 01:36:09 2024 - 00:12 ago
* 2024-01-21 01:36:21 (4264) [INFO]     State  : Running, pid: 924945
* 2024-01-21 01:36:23 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-21 01:36:23 (4264) [INFO]   The other application is: yum
* 2024-01-21 01:36:23 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-21 01:36:23 (4264) [INFO]     Started: Sun Jan 21 01:36:09 2024 - 00:14 ago
* 2024-01-21 01:36:23 (4264) [INFO]     State  : Sleeping, pid: 924945
* 2024-01-21 01:36:25 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-21 01:36:25 (4264) [INFO]   The other application is: yum
* 2024-01-21 01:36:25 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-21 01:36:25 (4264) [INFO]     Started: Sun Jan 21 01:36:09 2024 - 00:16 ago
* 2024-01-21 01:36:25 (4264) [INFO]     State  : Sleeping, pid: 924945
* 2024-01-21 01:36:27 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-21 01:36:27 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-21 01:36:27 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-21 01:36:27 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-21 01:36:27 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-21 01:36:27 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-21 01:36:27 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-21 01:36:27 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-21 01:36:27 (4264) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-01-21 01:36:27 (4281) [INFO] 
* 2024-01-21 01:36:27 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-21 01:36:27 (4251) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-21 01:36:33 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-21 01:36:33 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-21 01:36:33 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-21 01:36:33 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-21 01:36:33 (4264) [INFO] Trying other mirror.
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-21 01:36:33 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-21 01:36:33 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-21 01:36:33 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-21 01:36:33 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-21 01:36:33 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-21 01:36:33 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-21 01:36:33 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-21 01:36:33 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-21 01:36:33 (4264) [INFO]         or
* 2024-01-21 01:36:33 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-21 01:36:33 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-21 01:36:33 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-21 01:36:33 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-21 01:36:33 (4264) [INFO]         compromise:
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-21 01:36:33 (4264) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-21 01:36:33 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-21 01:36:33 (4281) [INFO] 
* 2024-01-21 01:36:33 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-21 01:36:33 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-21 01:36:33 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-21 01:36:35 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-21 01:36:35 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-21 01:36:35 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-21 01:36:35 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-21 01:36:35 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-21 01:36:35 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-21 01:36:35 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-21 01:36:35 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-21 01:36:35 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-21 01:36:40 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-21 01:36:40 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-21 01:36:40 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-21 01:36:40 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-21 01:36:40 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-21 01:36:40 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-21 01:36:40 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o652Avzk1c/ea_profile.json
* 2024-01-21 01:36:46 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o652Avzk1c/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-21 01:36:46 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-22 01:33:56 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-22 01:33:57 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-22 01:33:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-22 01:33:58 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-22 01:33:58 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-22 01:33:58 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-22 01:33:58 (4251) [INFO] 
* 2024-01-22 01:33:58 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-22 01:33:59 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 635703.
* 2024-01-22 01:33:59 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:33:59 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:33:59 (4264) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-01-22 01:33:59 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:07 ago
* 2024-01-22 01:33:59 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:01 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:01 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:01 (4264) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:01 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:09 ago
* 2024-01-22 01:34:01 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:03 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:03 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:03 (4264) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:03 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:11 ago
* 2024-01-22 01:34:03 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:05 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:05 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:05 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:05 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:13 ago
* 2024-01-22 01:34:05 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:07 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:07 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:07 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:07 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:15 ago
* 2024-01-22 01:34:07 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:09 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:09 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:09 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:09 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:17 ago
* 2024-01-22 01:34:09 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:11 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:11 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:11 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:11 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:19 ago
* 2024-01-22 01:34:11 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:13 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:13 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:13 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:13 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:21 ago
* 2024-01-22 01:34:13 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:15 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:15 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:15 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:15 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:23 ago
* 2024-01-22 01:34:15 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:17 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:17 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:17 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:17 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:25 ago
* 2024-01-22 01:34:17 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:19 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:19 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:19 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:19 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:27 ago
* 2024-01-22 01:34:19 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:21 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:21 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:21 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:21 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:29 ago
* 2024-01-22 01:34:21 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:23 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:23 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:23 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:23 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:31 ago
* 2024-01-22 01:34:23 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:25 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:25 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:25 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:25 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:33 ago
* 2024-01-22 01:34:25 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:27 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:27 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:27 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:27 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:35 ago
* 2024-01-22 01:34:27 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:29 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:29 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:29 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:29 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:37 ago
* 2024-01-22 01:34:29 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:31 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:31 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:31 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:31 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:39 ago
* 2024-01-22 01:34:31 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:33 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:33 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:33 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:33 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:41 ago
* 2024-01-22 01:34:33 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:35 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:35 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:35 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:35 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:43 ago
* 2024-01-22 01:34:35 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:37 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:37 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:37 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:37 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:45 ago
* 2024-01-22 01:34:37 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:39 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:39 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:39 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:39 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:47 ago
* 2024-01-22 01:34:39 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:41 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:41 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:41 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:41 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:49 ago
* 2024-01-22 01:34:41 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:43 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:43 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:43 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:43 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:51 ago
* 2024-01-22 01:34:43 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:45 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:45 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:45 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:45 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:53 ago
* 2024-01-22 01:34:45 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:47 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:47 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:47 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:47 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:55 ago
* 2024-01-22 01:34:47 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:49 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:49 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:49 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:49 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:57 ago
* 2024-01-22 01:34:49 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:51 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:51 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:51 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:51 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 00:59 ago
* 2024-01-22 01:34:51 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:53 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:53 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:53 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:53 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:01 ago
* 2024-01-22 01:34:53 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:55 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:55 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:55 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:55 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:03 ago
* 2024-01-22 01:34:55 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:57 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:57 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:57 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:57 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:05 ago
* 2024-01-22 01:34:57 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:34:59 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:34:59 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:34:59 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:34:59 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:07 ago
* 2024-01-22 01:34:59 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:01 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:01 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:01 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:01 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:09 ago
* 2024-01-22 01:35:01 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:03 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:03 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:03 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:03 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:11 ago
* 2024-01-22 01:35:03 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:05 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:05 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:05 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:05 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:13 ago
* 2024-01-22 01:35:05 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:07 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:07 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:07 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:07 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:15 ago
* 2024-01-22 01:35:07 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:09 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:09 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:09 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:09 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:17 ago
* 2024-01-22 01:35:09 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:11 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:11 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:11 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:11 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:19 ago
* 2024-01-22 01:35:11 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:13 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:13 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:13 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:13 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:21 ago
* 2024-01-22 01:35:13 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:15 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:15 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:15 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:15 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:23 ago
* 2024-01-22 01:35:15 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:17 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:17 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:17 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:17 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:25 ago
* 2024-01-22 01:35:17 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:19 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:19 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:19 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:19 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:27 ago
* 2024-01-22 01:35:19 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:21 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:21 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:21 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:21 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:29 ago
* 2024-01-22 01:35:21 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:23 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:23 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:23 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:23 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:31 ago
* 2024-01-22 01:35:23 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:25 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:25 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:25 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:25 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:33 ago
* 2024-01-22 01:35:25 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:27 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:27 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:27 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:27 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:35 ago
* 2024-01-22 01:35:27 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:29 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:29 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:29 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:29 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:37 ago
* 2024-01-22 01:35:29 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:31 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:31 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:31 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:31 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:39 ago
* 2024-01-22 01:35:31 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:33 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:33 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:33 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:33 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:41 ago
* 2024-01-22 01:35:33 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:35 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:35 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:35 (4264) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-22 01:35:35 (4264) [INFO]     Started: Mon Jan 22 01:33:52 2024 - 01:43 ago
* 2024-01-22 01:35:35 (4264) [INFO]     State  : Sleeping, pid: 635703
* 2024-01-22 01:35:37 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 639840.
* 2024-01-22 01:35:37 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:37 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:37 (4264) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-01-22 01:35:37 (4264) [INFO]     Started: Mon Jan 22 01:35:35 2024 - 00:02 ago
* 2024-01-22 01:35:37 (4264) [INFO]     State  : Sleeping, pid: 639840
* 2024-01-22 01:35:39 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-22 01:35:39 (4264) [INFO]   The other application is: yum
* 2024-01-22 01:35:39 (4264) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-01-22 01:35:39 (4264) [INFO]     Started: Mon Jan 22 01:35:35 2024 - 00:04 ago
* 2024-01-22 01:35:39 (4264) [INFO]     State  : Running, pid: 639840
* 2024-01-22 01:35:41 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-22 01:35:41 (4264) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-22 01:35:41 (4264) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-22 01:35:41 (4264) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-22 01:35:41 (4264) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-22 01:35:41 (4264) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-22 01:35:41 (4264) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-22 01:35:41 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-22 01:35:41 (4264) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-22 01:35:41 (4281) [INFO] 
* 2024-01-22 01:35:41 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-22 01:35:41 (4251) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-22 01:35:48 (4264) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-22 01:35:48 (4264) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-22 01:35:48 (4264) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-22 01:35:48 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-22 01:35:48 (4264) [INFO] Trying other mirror.
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-22 01:35:48 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-22 01:35:48 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-22 01:35:48 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-22 01:35:48 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-22 01:35:48 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-22 01:35:48 (4264) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-22 01:35:48 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-22 01:35:48 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-22 01:35:48 (4264) [INFO]         or
* 2024-01-22 01:35:48 (4264) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-22 01:35:48 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-22 01:35:48 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-22 01:35:48 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-22 01:35:48 (4264) [INFO]         compromise:
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-22 01:35:48 (4264) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-22 01:35:48 (4264) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-22 01:35:48 (4281) [INFO] 
* 2024-01-22 01:35:48 (4264) [INFO] Is this ok [y/N]: 
* 2024-01-22 01:35:48 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-22 01:35:48 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-22 01:35:51 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-22 01:35:51 (1710) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-22 01:35:51 (1710) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-22 01:35:51 (1693) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-22 01:35:51 (1693) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-22 01:35:51 (1710) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-22 01:35:51 (1710) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-22 01:35:51 (1693) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-22 01:35:51 (1710) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-22 01:35:54 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-22 01:35:54 (1634) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-22 01:35:54 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-22 01:35:54 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-22 01:35:54 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-22 01:35:55 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-22 01:35:55 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/90zyC74Mr5/ea_profile.json
* 2024-01-22 01:36:00 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/90zyC74Mr5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-22 01:36:00 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-23 01:34:24 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-23 01:34:24 (161) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-01-23 01:34:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-23 01:34:26 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-23 01:34:26 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-23 01:34:26 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-23 01:34:26 (4319) [INFO] 
* 2024-01-23 01:34:26 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-23 01:34:26 (4332) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 714019.
* 2024-01-23 01:34:26 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:26 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:26 (4332) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-23 01:34:26 (4332) [INFO]     Started: Tue Jan 23 01:34:21 2024 - 00:05 ago
* 2024-01-23 01:34:26 (4332) [INFO]     State  : Sleeping, pid: 714019
* 2024-01-23 01:34:28 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:28 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:28 (4332) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-23 01:34:28 (4332) [INFO]     Started: Tue Jan 23 01:34:21 2024 - 00:07 ago
* 2024-01-23 01:34:28 (4332) [INFO]     State  : Sleeping, pid: 714019
* 2024-01-23 01:34:30 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:30 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:30 (4332) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-23 01:34:30 (4332) [INFO]     Started: Tue Jan 23 01:34:21 2024 - 00:09 ago
* 2024-01-23 01:34:30 (4332) [INFO]     State  : Sleeping, pid: 714019
* 2024-01-23 01:34:32 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:32 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:32 (4332) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-23 01:34:32 (4332) [INFO]     Started: Tue Jan 23 01:34:21 2024 - 00:11 ago
* 2024-01-23 01:34:32 (4332) [INFO]     State  : Sleeping, pid: 714019
* 2024-01-23 01:34:34 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:34 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:34 (4332) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-23 01:34:34 (4332) [INFO]     Started: Tue Jan 23 01:34:21 2024 - 00:13 ago
* 2024-01-23 01:34:34 (4332) [INFO]     State  : Sleeping, pid: 714019
* 2024-01-23 01:34:36 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:36 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:36 (4332) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-23 01:34:36 (4332) [INFO]     Started: Tue Jan 23 01:34:21 2024 - 00:15 ago
* 2024-01-23 01:34:36 (4332) [INFO]     State  : Sleeping, pid: 714019
* 2024-01-23 01:34:38 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-23 01:34:38 (4332) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-23 01:34:38 (4332) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-23 01:34:38 (4332) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-23 01:34:38 (4332) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-23 01:34:38 (4332) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-23 01:34:38 (4332) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-23 01:34:38 (4332) [INFO] Cleaning up list of fastest mirrors
* 2024-01-23 01:34:38 (4332) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-01-23 01:34:38 (4349) [INFO] 
* 2024-01-23 01:34:38 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-23 01:34:38 (4319) [INFO] 
* 2024-01-23 01:34:39 (4332) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 714677.
* 2024-01-23 01:34:39 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:39 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:39 (4332) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-01-23 01:34:39 (4332) [INFO]     Started: Tue Jan 23 01:34:37 2024 - 00:02 ago
* 2024-01-23 01:34:39 (4332) [INFO]     State  : Sleeping, pid: 714677
* 2024-01-23 01:34:41 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:41 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:41 (4332) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-23 01:34:41 (4332) [INFO]     Started: Tue Jan 23 01:34:37 2024 - 00:04 ago
* 2024-01-23 01:34:41 (4332) [INFO]     State  : Sleeping, pid: 714677
* 2024-01-23 01:34:43 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-23 01:34:43 (4332) [INFO]   The other application is: yum
* 2024-01-23 01:34:43 (4332) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-23 01:34:43 (4332) [INFO]     Started: Tue Jan 23 01:34:37 2024 - 00:06 ago
* 2024-01-23 01:34:43 (4332) [INFO]     State  : Sleeping, pid: 714677
* 2024-01-23 01:34:49 (4332) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-23 01:34:49 (4332) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-23 01:34:49 (4332) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-23 01:34:49 (4332) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-23 01:34:49 (4332) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-23 01:34:49 (4332) [INFO] Trying other mirror.
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-23 01:34:49 (4332) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-23 01:34:49 (4332) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-23 01:34:49 (4332) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-23 01:34:49 (4332) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-23 01:34:49 (4332) [INFO]         packages for the previous distribution release still work).
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-23 01:34:49 (4332) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-23 01:34:49 (4332) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-23 01:34:49 (4332) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-23 01:34:49 (4332) [INFO]         or
* 2024-01-23 01:34:49 (4332) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-23 01:34:49 (4332) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-23 01:34:49 (4332) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-23 01:34:49 (4332) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-23 01:34:49 (4332) [INFO]         compromise:
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-23 01:34:49 (4332) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-23 01:34:49 (4332) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-23 01:34:49 (4349) [INFO] 
* 2024-01-23 01:34:49 (4332) [INFO] Is this ok [y/N]: 
* 2024-01-23 01:34:49 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-23 01:34:49 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-23 01:34:50 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-23 01:34:50 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-23 01:34:50 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-23 01:34:50 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-23 01:34:50 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-23 01:34:50 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-23 01:34:50 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-23 01:34:50 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-23 01:34:50 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-23 01:34:53 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-23 01:34:53 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-23 01:34:53 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-23 01:34:53 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-23 01:34:53 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-23 01:34:54 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-23 01:34:54 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hhV3Fjf3NN/ea_profile.json
* 2024-01-23 01:34:58 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hhV3Fjf3NN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2362.
* 2024-01-23 01:34:58 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-24 01:33:36 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-24 01:33:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-24 01:33:37 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-24 01:33:37 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-24 01:33:37 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-24 01:33:37 (4319) [INFO] 
* 2024-01-24 01:33:37 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-24 01:33:37 (4332) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 84693.
* 2024-01-24 01:33:37 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-24 01:33:37 (4332) [INFO]   The other application is: yum
* 2024-01-24 01:33:37 (4332) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-24 01:33:37 (4332) [INFO]     Started: Wed Jan 24 01:33:33 2024 - 00:04 ago
* 2024-01-24 01:33:37 (4332) [INFO]     State  : Sleeping, pid: 84693
* 2024-01-24 01:33:39 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-24 01:33:39 (4332) [INFO]   The other application is: yum
* 2024-01-24 01:33:39 (4332) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-24 01:33:39 (4332) [INFO]     Started: Wed Jan 24 01:33:33 2024 - 00:06 ago
* 2024-01-24 01:33:39 (4332) [INFO]     State  : Sleeping, pid: 84693
* 2024-01-24 01:33:41 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-24 01:33:41 (4332) [INFO]   The other application is: yum
* 2024-01-24 01:33:41 (4332) [INFO]     Memory :  38 M RSS (3.1 GB VSZ)
* 2024-01-24 01:33:41 (4332) [INFO]     Started: Wed Jan 24 01:33:33 2024 - 00:08 ago
* 2024-01-24 01:33:41 (4332) [INFO]     State  : Sleeping, pid: 84693
* 2024-01-24 01:33:43 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-24 01:33:43 (4332) [INFO]   The other application is: yum
* 2024-01-24 01:33:43 (4332) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-01-24 01:33:43 (4332) [INFO]     Started: Wed Jan 24 01:33:33 2024 - 00:10 ago
* 2024-01-24 01:33:43 (4332) [INFO]     State  : Sleeping, pid: 84693
* 2024-01-24 01:33:45 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-24 01:33:45 (4332) [INFO]   The other application is: yum
* 2024-01-24 01:33:45 (4332) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-24 01:33:45 (4332) [INFO]     Started: Wed Jan 24 01:33:33 2024 - 00:12 ago
* 2024-01-24 01:33:45 (4332) [INFO]     State  : Running, pid: 84693
* 2024-01-24 01:33:47 (4332) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 85167.
* 2024-01-24 01:33:47 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-24 01:33:48 (4332) [INFO]   The other application is: yum
* 2024-01-24 01:33:48 (4332) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-01-24 01:33:48 (4332) [INFO]     Started: Wed Jan 24 01:33:47 2024 - 00:00 ago
* 2024-01-24 01:33:48 (4332) [INFO]     State  : Sleeping, pid: 85167
* 2024-01-24 01:33:50 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-24 01:33:50 (4332) [INFO]   The other application is: yum
* 2024-01-24 01:33:50 (4332) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-01-24 01:33:50 (4332) [INFO]     Started: Wed Jan 24 01:33:47 2024 - 00:03 ago
* 2024-01-24 01:33:50 (4332) [INFO]     State  : Sleeping, pid: 85167
* 2024-01-24 01:33:52 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-24 01:33:52 (4332) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-24 01:33:52 (4332) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-24 01:33:52 (4332) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-24 01:33:52 (4332) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-24 01:33:52 (4332) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-24 01:33:52 (4332) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-24 01:33:52 (4332) [INFO] Cleaning up list of fastest mirrors
* 2024-01-24 01:33:52 (4332) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-24 01:33:52 (4349) [INFO] 
* 2024-01-24 01:33:52 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-24 01:33:52 (4319) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-24 01:33:58 (4332) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-24 01:33:58 (4332) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-24 01:33:58 (4332) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-24 01:33:58 (4332) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-24 01:33:58 (4332) [INFO] Trying other mirror.
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-24 01:33:58 (4332) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-24 01:33:58 (4332) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-24 01:33:58 (4332) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-24 01:33:58 (4332) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-24 01:33:58 (4332) [INFO]         packages for the previous distribution release still work).
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-24 01:33:58 (4332) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-24 01:33:58 (4332) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-24 01:33:58 (4332) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-24 01:33:58 (4332) [INFO]         or
* 2024-01-24 01:33:58 (4332) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-24 01:33:58 (4332) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-24 01:33:58 (4332) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-24 01:33:58 (4332) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-24 01:33:58 (4332) [INFO]         compromise:
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-24 01:33:58 (4332) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-24 01:33:58 (4332) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-24 01:33:58 (4349) [INFO] 
* 2024-01-24 01:33:58 (4332) [INFO] Is this ok [y/N]: 
* 2024-01-24 01:33:58 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-24 01:33:58 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-24 01:34:00 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-24 01:34:00 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-24 01:34:00 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-24 01:34:00 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-24 01:34:00 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-24 01:34:00 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-24 01:34:00 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-24 01:34:00 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-24 01:34:00 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-24 01:34:03 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-24 01:34:03 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-24 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-24 01:34:03 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-24 01:34:03 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-24 01:34:04 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-24 01:34:04 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/spFFxJAHOU/ea_profile.json
* 2024-01-24 01:34:09 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/spFFxJAHOU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2362.
* 2024-01-24 01:34:09 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-25 01:34:19 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-25 01:34:19 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-25 01:34:20 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-25 01:34:20 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-25 01:34:20 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-25 01:34:20 (4319) [INFO] 
* 2024-01-25 01:34:21 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-25 01:34:21 (4332) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 774581.
* 2024-01-25 01:34:21 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-25 01:34:21 (4332) [INFO]   The other application is: yum
* 2024-01-25 01:34:21 (4332) [INFO]     Memory :  38 M RSS (2.9 GB VSZ)
* 2024-01-25 01:34:21 (4332) [INFO]     Started: Thu Jan 25 01:34:17 2024 - 00:04 ago
* 2024-01-25 01:34:21 (4332) [INFO]     State  : Sleeping, pid: 774581
* 2024-01-25 01:34:23 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-25 01:34:23 (4332) [INFO]   The other application is: yum
* 2024-01-25 01:34:23 (4332) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-25 01:34:23 (4332) [INFO]     Started: Thu Jan 25 01:34:17 2024 - 00:06 ago
* 2024-01-25 01:34:23 (4332) [INFO]     State  : Sleeping, pid: 774581
* 2024-01-25 01:34:25 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-25 01:34:25 (4332) [INFO]   The other application is: yum
* 2024-01-25 01:34:25 (4332) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-25 01:34:25 (4332) [INFO]     Started: Thu Jan 25 01:34:17 2024 - 00:08 ago
* 2024-01-25 01:34:25 (4332) [INFO]     State  : Sleeping, pid: 774581
* 2024-01-25 01:34:27 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-25 01:34:27 (4332) [INFO]   The other application is: yum
* 2024-01-25 01:34:27 (4332) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-25 01:34:27 (4332) [INFO]     Started: Thu Jan 25 01:34:17 2024 - 00:10 ago
* 2024-01-25 01:34:27 (4332) [INFO]     State  : Sleeping, pid: 774581
* 2024-01-25 01:34:29 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-25 01:34:29 (4332) [INFO]   The other application is: yum
* 2024-01-25 01:34:29 (4332) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-25 01:34:29 (4332) [INFO]     Started: Thu Jan 25 01:34:17 2024 - 00:12 ago
* 2024-01-25 01:34:29 (4332) [INFO]     State  : Sleeping, pid: 774581
* 2024-01-25 01:34:31 (4332) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 775106.
* 2024-01-25 01:34:31 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-25 01:34:31 (4332) [INFO]   The other application is: yum
* 2024-01-25 01:34:31 (4332) [INFO]     Memory :  36 M RSS (331 MB VSZ)
* 2024-01-25 01:34:31 (4332) [INFO]     Started: Thu Jan 25 01:34:30 2024 - 00:01 ago
* 2024-01-25 01:34:31 (4332) [INFO]     State  : Sleeping, pid: 775106
* 2024-01-25 01:34:33 (4332) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-25 01:34:33 (4332) [INFO]   The other application is: yum
* 2024-01-25 01:34:33 (4332) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-01-25 01:34:33 (4332) [INFO]     Started: Thu Jan 25 01:34:30 2024 - 00:03 ago
* 2024-01-25 01:34:33 (4332) [INFO]     State  : Uninterruptible, pid: 775106
* 2024-01-25 01:34:35 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-25 01:34:35 (4332) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-25 01:34:35 (4332) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-25 01:34:35 (4332) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-25 01:34:35 (4332) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-25 01:34:35 (4332) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-25 01:34:35 (4332) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-25 01:34:35 (4332) [INFO] Cleaning up list of fastest mirrors
* 2024-01-25 01:34:35 (4332) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-25 01:34:35 (4349) [INFO] 
* 2024-01-25 01:34:35 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-25 01:34:35 (4319) [INFO] 
* 2024-01-25 01:35:16 (4332) [INFO] https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2024-01-25 01:35:16 (4332) [INFO] Trying other mirror.
* 2024-01-25 01:35:17 (4332) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-25 01:35:17 (4332) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-25 01:35:17 (4332) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-25 01:35:17 (4332) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-25 01:35:17 (4332) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-25 01:35:17 (4332) [INFO] Trying other mirror.
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-25 01:35:17 (4332) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-25 01:35:17 (4332) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-25 01:35:17 (4332) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-25 01:35:17 (4332) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-25 01:35:17 (4332) [INFO]         packages for the previous distribution release still work).
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-25 01:35:17 (4332) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-25 01:35:17 (4332) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-25 01:35:17 (4332) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-25 01:35:17 (4332) [INFO]         or
* 2024-01-25 01:35:17 (4332) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-25 01:35:17 (4332) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-25 01:35:17 (4332) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-25 01:35:17 (4332) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-25 01:35:17 (4332) [INFO]         compromise:
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-25 01:35:17 (4332) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-25 01:35:17 (4332) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-25 01:35:17 (4349) [INFO] 
* 2024-01-25 01:35:17 (4332) [INFO] Is this ok [y/N]: 
* 2024-01-25 01:35:17 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-25 01:35:17 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-25 01:35:19 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-25 01:35:19 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-25 01:35:19 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-25 01:35:19 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-25 01:35:19 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-25 01:35:19 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-25 01:35:19 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-25 01:35:19 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-25 01:35:19 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-25 01:35:23 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-25 01:35:23 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-25 01:35:23 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-25 01:35:23 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-25 01:35:23 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-25 01:35:23 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-25 01:35:23 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4IrJiip7f9/ea_profile.json
* 2024-01-25 01:35:28 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4IrJiip7f9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2362.
* 2024-01-25 01:35:28 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-26 01:33:34 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-26 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-26 01:33:35 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-26 01:33:35 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-26 01:33:35 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-26 01:33:35 (4322) [INFO] 
* 2024-01-26 01:33:35 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-26 01:33:35 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 364251.
* 2024-01-26 01:33:35 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-26 01:33:35 (4335) [INFO]   The other application is: yum
* 2024-01-26 01:33:35 (4335) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-26 01:33:35 (4335) [INFO]     Started: Fri Jan 26 01:33:31 2024 - 00:04 ago
* 2024-01-26 01:33:35 (4335) [INFO]     State  : Sleeping, pid: 364251
* 2024-01-26 01:33:37 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-26 01:33:37 (4335) [INFO]   The other application is: yum
* 2024-01-26 01:33:37 (4335) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-01-26 01:33:37 (4335) [INFO]     Started: Fri Jan 26 01:33:31 2024 - 00:06 ago
* 2024-01-26 01:33:37 (4335) [INFO]     State  : Sleeping, pid: 364251
* 2024-01-26 01:33:39 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-26 01:33:39 (4335) [INFO]   The other application is: yum
* 2024-01-26 01:33:39 (4335) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-26 01:33:39 (4335) [INFO]     Started: Fri Jan 26 01:33:31 2024 - 00:08 ago
* 2024-01-26 01:33:39 (4335) [INFO]     State  : Sleeping, pid: 364251
* 2024-01-26 01:33:41 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-26 01:33:41 (4335) [INFO]   The other application is: yum
* 2024-01-26 01:33:41 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-26 01:33:41 (4335) [INFO]     Started: Fri Jan 26 01:33:31 2024 - 00:10 ago
* 2024-01-26 01:33:41 (4335) [INFO]     State  : Sleeping, pid: 364251
* 2024-01-26 01:33:43 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 364658.
* 2024-01-26 01:33:43 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-26 01:33:43 (4335) [INFO]   The other application is: yum
* 2024-01-26 01:33:43 (4335) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-01-26 01:33:43 (4335) [INFO]     Started: Fri Jan 26 01:33:42 2024 - 00:01 ago
* 2024-01-26 01:33:43 (4335) [INFO]     State  : Sleeping, pid: 364658
* 2024-01-26 01:33:45 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-26 01:33:45 (4335) [INFO]   The other application is: yum
* 2024-01-26 01:33:45 (4335) [INFO]     Memory :  39 M RSS (741 MB VSZ)
* 2024-01-26 01:33:45 (4335) [INFO]     Started: Fri Jan 26 01:33:42 2024 - 00:03 ago
* 2024-01-26 01:33:45 (4335) [INFO]     State  : Sleeping, pid: 364658
* 2024-01-26 01:33:47 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-26 01:33:47 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-26 01:33:47 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-26 01:33:47 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-26 01:33:47 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-26 01:33:47 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-26 01:33:47 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-26 01:33:47 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-01-26 01:33:47 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-26 01:33:47 (4352) [INFO] 
* 2024-01-26 01:33:47 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-26 01:33:47 (4322) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-26 01:33:56 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-26 01:33:56 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-26 01:33:56 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-26 01:33:56 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-26 01:33:56 (4335) [INFO] Trying other mirror.
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-26 01:33:56 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-26 01:33:56 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-26 01:33:56 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-26 01:33:56 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-26 01:33:56 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-26 01:33:56 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-26 01:33:56 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-26 01:33:56 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-26 01:33:56 (4335) [INFO]         or
* 2024-01-26 01:33:56 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-26 01:33:56 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-26 01:33:56 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-26 01:33:56 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-26 01:33:56 (4335) [INFO]         compromise:
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-26 01:33:56 (4335) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-26 01:33:56 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-26 01:33:56 (4352) [INFO] 
* 2024-01-26 01:33:56 (4335) [INFO] Is this ok [y/N]: 
* 2024-01-26 01:33:56 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-26 01:33:56 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-26 01:33:57 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-26 01:33:57 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-26 01:33:57 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-26 01:33:57 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-26 01:33:57 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-26 01:33:57 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-26 01:33:57 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-26 01:33:57 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-26 01:33:57 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-26 01:33:59 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-26 01:33:59 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-26 01:33:59 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-26 01:33:59 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-26 01:33:59 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-26 01:34:00 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-26 01:34:00 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KqJCbQNodE/ea_profile.json
* 2024-01-26 01:34:02 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KqJCbQNodE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-26 01:34:02 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-27 01:34:28 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-27 01:34:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-27 01:34:29 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-27 01:34:29 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-27 01:34:29 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-27 01:34:29 (4322) [INFO] 
* 2024-01-27 01:34:29 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-27 01:34:29 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 11075.
* 2024-01-27 01:34:29 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-27 01:34:29 (4335) [INFO]   The other application is: yum
* 2024-01-27 01:34:29 (4335) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-27 01:34:29 (4335) [INFO]     Started: Sat Jan 27 01:34:24 2024 - 00:05 ago
* 2024-01-27 01:34:29 (4335) [INFO]     State  : Sleeping, pid: 11075
* 2024-01-27 01:34:31 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-27 01:34:31 (4335) [INFO]   The other application is: yum
* 2024-01-27 01:34:31 (4335) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-27 01:34:31 (4335) [INFO]     Started: Sat Jan 27 01:34:24 2024 - 00:07 ago
* 2024-01-27 01:34:31 (4335) [INFO]     State  : Sleeping, pid: 11075
* 2024-01-27 01:34:33 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-27 01:34:33 (4335) [INFO]   The other application is: yum
* 2024-01-27 01:34:33 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-01-27 01:34:33 (4335) [INFO]     Started: Sat Jan 27 01:34:24 2024 - 00:09 ago
* 2024-01-27 01:34:33 (4335) [INFO]     State  : Sleeping, pid: 11075
* 2024-01-27 01:34:35 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 11538.
* 2024-01-27 01:34:35 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-27 01:34:35 (4335) [INFO]   The other application is: yum
* 2024-01-27 01:34:35 (4335) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-01-27 01:34:35 (4335) [INFO]     Started: Sat Jan 27 01:34:33 2024 - 00:02 ago
* 2024-01-27 01:34:35 (4335) [INFO]     State  : Sleeping, pid: 11538
* 2024-01-27 01:34:37 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-27 01:34:37 (4335) [INFO]   The other application is: yum
* 2024-01-27 01:34:37 (4335) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-01-27 01:34:37 (4335) [INFO]     Started: Sat Jan 27 01:34:33 2024 - 00:04 ago
* 2024-01-27 01:34:37 (4335) [INFO]     State  : Sleeping, pid: 11538
* 2024-01-27 01:34:39 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-27 01:34:39 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-27 01:34:39 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-27 01:34:39 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-27 01:34:39 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-27 01:34:39 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-27 01:34:39 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-27 01:34:39 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-01-27 01:34:39 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-27 01:34:39 (4352) [INFO] 
* 2024-01-27 01:34:39 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-27 01:34:39 (4322) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-27 01:34:47 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-27 01:34:47 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-27 01:34:47 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-27 01:34:47 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-27 01:34:47 (4335) [INFO] Trying other mirror.
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-27 01:34:47 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-27 01:34:47 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-27 01:34:47 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-27 01:34:47 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-27 01:34:47 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-27 01:34:47 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-27 01:34:47 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-27 01:34:47 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-27 01:34:47 (4335) [INFO]         or
* 2024-01-27 01:34:47 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-27 01:34:47 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-27 01:34:47 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-27 01:34:47 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-27 01:34:47 (4335) [INFO]         compromise:
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-27 01:34:47 (4335) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-27 01:34:47 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-27 01:34:47 (4352) [INFO] 
* 2024-01-27 01:34:47 (4335) [INFO] Is this ok [y/N]: 
* 2024-01-27 01:34:47 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-27 01:34:47 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-27 01:34:48 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-27 01:34:48 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-27 01:34:48 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-27 01:34:48 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-27 01:34:48 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-27 01:34:48 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-27 01:34:48 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-27 01:34:48 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-27 01:34:48 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-27 01:34:51 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-27 01:34:51 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-27 01:34:51 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-27 01:34:51 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-27 01:34:51 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-27 01:34:52 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-27 01:34:52 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W5EF8Uz9up/ea_profile.json
* 2024-01-27 01:34:55 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W5EF8Uz9up/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-27 01:34:55 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-28 01:34:35 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-28 01:34:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-28 01:34:37 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-28 01:34:37 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-28 01:34:37 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-28 01:34:37 (4322) [INFO] 
* 2024-01-28 01:34:37 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-28 01:34:37 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 412550.
* 2024-01-28 01:34:37 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-28 01:34:37 (4335) [INFO]   The other application is: yum
* 2024-01-28 01:34:37 (4335) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-01-28 01:34:37 (4335) [INFO]     Started: Sun Jan 28 01:34:32 2024 - 00:05 ago
* 2024-01-28 01:34:37 (4335) [INFO]     State  : Sleeping, pid: 412550
* 2024-01-28 01:34:39 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-28 01:34:39 (4335) [INFO]   The other application is: yum
* 2024-01-28 01:34:39 (4335) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-01-28 01:34:39 (4335) [INFO]     Started: Sun Jan 28 01:34:32 2024 - 00:07 ago
* 2024-01-28 01:34:39 (4335) [INFO]     State  : Sleeping, pid: 412550
* 2024-01-28 01:34:41 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-28 01:34:41 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-28 01:34:41 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-28 01:34:41 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-28 01:34:41 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-28 01:34:41 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-28 01:34:41 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-28 01:34:41 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-01-28 01:34:41 (4335) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-01-28 01:34:41 (4352) [INFO] 
* 2024-01-28 01:34:41 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-28 01:34:41 (4322) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-28 01:34:53 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-28 01:34:53 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-28 01:34:53 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-28 01:34:53 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-28 01:34:53 (4335) [INFO] Trying other mirror.
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-28 01:34:53 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-28 01:34:53 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-28 01:34:53 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-28 01:34:53 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-28 01:34:53 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-28 01:34:53 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-28 01:34:53 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-28 01:34:53 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-28 01:34:53 (4335) [INFO]         or
* 2024-01-28 01:34:53 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-28 01:34:53 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-28 01:34:53 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-28 01:34:53 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-28 01:34:53 (4335) [INFO]         compromise:
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-28 01:34:53 (4335) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-28 01:34:53 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-28 01:34:53 (4352) [INFO] 
* 2024-01-28 01:34:53 (4335) [INFO] Is this ok [y/N]: 
* 2024-01-28 01:34:53 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-28 01:34:53 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-28 01:34:58 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-28 01:34:58 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-28 01:34:58 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-28 01:34:58 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-28 01:34:58 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-28 01:34:58 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-28 01:34:58 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-28 01:34:58 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-28 01:34:58 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-28 01:35:02 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-28 01:35:02 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-28 01:35:02 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-28 01:35:02 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-28 01:35:02 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-28 01:35:03 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-28 01:35:03 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RRP88PIBMy/ea_profile.json
* 2024-01-28 01:35:07 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RRP88PIBMy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-28 01:35:07 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-29 01:33:26 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-29 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-29 01:33:27 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-29 01:33:27 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-29 01:33:27 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-29 01:33:27 (4322) [INFO] 
* 2024-01-29 01:33:27 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-29 01:33:27 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 874605.
* 2024-01-29 01:33:27 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-29 01:33:27 (4335) [INFO]   The other application is: yum
* 2024-01-29 01:33:27 (4335) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-01-29 01:33:27 (4335) [INFO]     Started: Mon Jan 29 01:33:23 2024 - 00:04 ago
* 2024-01-29 01:33:27 (4335) [INFO]     State  : Sleeping, pid: 874605
* 2024-01-29 01:33:29 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-29 01:33:29 (4335) [INFO]   The other application is: yum
* 2024-01-29 01:33:29 (4335) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-01-29 01:33:29 (4335) [INFO]     Started: Mon Jan 29 01:33:23 2024 - 00:06 ago
* 2024-01-29 01:33:29 (4335) [INFO]     State  : Sleeping, pid: 874605
* 2024-01-29 01:33:31 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-29 01:33:31 (4335) [INFO]   The other application is: yum
* 2024-01-29 01:33:31 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-01-29 01:33:31 (4335) [INFO]     Started: Mon Jan 29 01:33:23 2024 - 00:08 ago
* 2024-01-29 01:33:31 (4335) [INFO]     State  : Running, pid: 874605
* 2024-01-29 01:33:33 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 874949.
* 2024-01-29 01:33:33 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-29 01:33:33 (4335) [INFO]   The other application is: yum
* 2024-01-29 01:33:33 (4335) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-01-29 01:33:33 (4335) [INFO]     Started: Mon Jan 29 01:33:31 2024 - 00:02 ago
* 2024-01-29 01:33:33 (4335) [INFO]     State  : Sleeping, pid: 874949
* 2024-01-29 01:33:35 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-29 01:33:35 (4335) [INFO]   The other application is: yum
* 2024-01-29 01:33:35 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-01-29 01:33:35 (4335) [INFO]     Started: Mon Jan 29 01:33:31 2024 - 00:04 ago
* 2024-01-29 01:33:35 (4335) [INFO]     State  : Sleeping, pid: 874949
* 2024-01-29 01:33:37 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-29 01:33:37 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-29 01:33:37 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-29 01:33:37 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-29 01:33:37 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-29 01:33:37 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-29 01:33:37 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-29 01:33:37 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-01-29 01:33:37 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-29 01:33:37 (4352) [INFO] 
* 2024-01-29 01:33:37 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-29 01:33:37 (4322) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-29 01:33:43 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-29 01:33:43 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-29 01:33:43 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-29 01:33:43 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-29 01:33:43 (4335) [INFO] Trying other mirror.
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-29 01:33:43 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-29 01:33:43 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-29 01:33:43 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-29 01:33:43 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-29 01:33:43 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-29 01:33:43 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-29 01:33:43 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-29 01:33:43 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-29 01:33:43 (4335) [INFO]         or
* 2024-01-29 01:33:43 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-29 01:33:43 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-29 01:33:43 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-29 01:33:43 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-29 01:33:43 (4335) [INFO]         compromise:
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-29 01:33:43 (4335) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-29 01:33:43 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-29 01:33:43 (4352) [INFO] 
* 2024-01-29 01:33:43 (4335) [INFO] Is this ok [y/N]: 
* 2024-01-29 01:33:43 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-29 01:33:43 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-29 01:33:44 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-29 01:33:44 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-29 01:33:44 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-29 01:33:44 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-29 01:33:44 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-29 01:33:44 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-29 01:33:44 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-29 01:33:44 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-29 01:33:44 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-29 01:33:47 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-29 01:33:47 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-29 01:33:47 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-29 01:33:47 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-29 01:33:47 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-29 01:33:48 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-29 01:33:48 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OXsgVkZfe5/ea_profile.json
* 2024-01-29 01:33:51 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OXsgVkZfe5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-29 01:33:51 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-30 01:33:40 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-30 01:33:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-30 01:33:41 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-30 01:33:41 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-30 01:33:41 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-30 01:33:41 (4322) [INFO] 
* 2024-01-30 01:33:41 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-30 01:33:42 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 260313.
* 2024-01-30 01:33:42 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-30 01:33:42 (4335) [INFO]   The other application is: yum
* 2024-01-30 01:33:42 (4335) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-01-30 01:33:42 (4335) [INFO]     Started: Tue Jan 30 01:33:37 2024 - 00:05 ago
* 2024-01-30 01:33:42 (4335) [INFO]     State  : Sleeping, pid: 260313
* 2024-01-30 01:33:44 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-30 01:33:44 (4335) [INFO]   The other application is: yum
* 2024-01-30 01:33:44 (4335) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-01-30 01:33:44 (4335) [INFO]     Started: Tue Jan 30 01:33:37 2024 - 00:07 ago
* 2024-01-30 01:33:44 (4335) [INFO]     State  : Sleeping, pid: 260313
* 2024-01-30 01:33:46 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-30 01:33:46 (4335) [INFO]   The other application is: yum
* 2024-01-30 01:33:46 (4335) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-01-30 01:33:46 (4335) [INFO]     Started: Tue Jan 30 01:33:37 2024 - 00:09 ago
* 2024-01-30 01:33:46 (4335) [INFO]     State  : Sleeping, pid: 260313
* 2024-01-30 01:33:48 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-30 01:33:48 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-30 01:33:48 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-30 01:33:48 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-30 01:33:48 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-30 01:33:48 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-30 01:33:48 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-30 01:33:48 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-01-30 01:33:48 (4335) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-01-30 01:33:48 (4352) [INFO] 
* 2024-01-30 01:33:48 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-30 01:33:48 (4322) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-30 01:33:57 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-30 01:33:57 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-30 01:33:57 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-30 01:33:57 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-30 01:33:57 (4335) [INFO] Trying other mirror.
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-30 01:33:57 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-30 01:33:57 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-30 01:33:57 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-30 01:33:57 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-30 01:33:57 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-30 01:33:57 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-30 01:33:57 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-30 01:33:57 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-30 01:33:57 (4335) [INFO]         or
* 2024-01-30 01:33:57 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-30 01:33:57 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-30 01:33:57 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-30 01:33:57 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-30 01:33:57 (4335) [INFO]         compromise:
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-30 01:33:57 (4335) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-30 01:33:57 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-30 01:33:57 (4352) [INFO] 
* 2024-01-30 01:33:57 (4335) [INFO] Is this ok [y/N]: 
* 2024-01-30 01:33:57 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-30 01:33:57 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-30 01:33:58 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-30 01:33:58 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-30 01:33:58 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-30 01:33:58 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-30 01:33:58 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-30 01:33:58 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-30 01:33:58 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-30 01:33:58 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-30 01:33:58 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-30 01:34:02 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-30 01:34:02 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-30 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-30 01:34:02 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-30 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-30 01:34:02 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-30 01:34:02 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bfpfF7tcjr/ea_profile.json
* 2024-01-30 01:34:06 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bfpfF7tcjr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-30 01:34:06 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-31 01:33:37 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-01-31 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-01-31 01:33:37 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-01-31 01:33:37 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-31 01:33:37 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-31 01:33:37 (4322) [INFO] 
* 2024-01-31 01:33:38 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-31 01:33:38 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 687586.
* 2024-01-31 01:33:38 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-31 01:33:38 (4335) [INFO]   The other application is: yum
* 2024-01-31 01:33:38 (4335) [INFO]     Memory :  36 M RSS (3.0 GB VSZ)
* 2024-01-31 01:33:38 (4335) [INFO]     Started: Wed Jan 31 01:33:33 2024 - 00:05 ago
* 2024-01-31 01:33:38 (4335) [INFO]     State  : Sleeping, pid: 687586
* 2024-01-31 01:33:40 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-31 01:33:40 (4335) [INFO]   The other application is: yum
* 2024-01-31 01:33:40 (4335) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-01-31 01:33:40 (4335) [INFO]     Started: Wed Jan 31 01:33:33 2024 - 00:07 ago
* 2024-01-31 01:33:40 (4335) [INFO]     State  : Sleeping, pid: 687586
* 2024-01-31 01:33:42 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-31 01:33:42 (4335) [INFO]   The other application is: yum
* 2024-01-31 01:33:42 (4335) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-01-31 01:33:42 (4335) [INFO]     Started: Wed Jan 31 01:33:33 2024 - 00:09 ago
* 2024-01-31 01:33:42 (4335) [INFO]     State  : Running, pid: 687586
* 2024-01-31 01:33:44 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 687974.
* 2024-01-31 01:33:44 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-31 01:33:44 (4335) [INFO]   The other application is: yum
* 2024-01-31 01:33:44 (4335) [INFO]     Memory :  36 M RSS (331 MB VSZ)
* 2024-01-31 01:33:44 (4335) [INFO]     Started: Wed Jan 31 01:33:41 2024 - 00:03 ago
* 2024-01-31 01:33:44 (4335) [INFO]     State  : Sleeping, pid: 687974
* 2024-01-31 01:33:46 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-31 01:33:46 (4335) [INFO]   The other application is: yum
* 2024-01-31 01:33:46 (4335) [INFO]     Memory :  38 M RSS (1.0 GB VSZ)
* 2024-01-31 01:33:46 (4335) [INFO]     Started: Wed Jan 31 01:33:41 2024 - 00:05 ago
* 2024-01-31 01:33:46 (4335) [INFO]     State  : Sleeping, pid: 687974
* 2024-01-31 01:33:48 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-31 01:33:48 (4335) [INFO]   The other application is: yum
* 2024-01-31 01:33:48 (4335) [INFO]     Memory :  39 M RSS (1.0 GB VSZ)
* 2024-01-31 01:33:48 (4335) [INFO]     Started: Wed Jan 31 01:33:41 2024 - 00:07 ago
* 2024-01-31 01:33:48 (4335) [INFO]     State  : Sleeping, pid: 687974
* 2024-01-31 01:33:50 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-01-31 01:33:50 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-01-31 01:33:50 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-01-31 01:33:50 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-01-31 01:33:50 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-01-31 01:33:50 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-01-31 01:33:50 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-01-31 01:33:50 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-01-31 01:33:50 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-01-31 01:33:50 (4352) [INFO] 
* 2024-01-31 01:33:50 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-31 01:33:50 (4322) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-01-31 01:33:58 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-01-31 01:33:58 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-01-31 01:33:58 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-01-31 01:33:58 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-31 01:33:58 (4335) [INFO] Trying other mirror.
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-01-31 01:33:58 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-31 01:33:58 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-31 01:33:58 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-31 01:33:58 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-31 01:33:58 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-31 01:33:58 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-31 01:33:58 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-31 01:33:58 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-01-31 01:33:58 (4335) [INFO]         or
* 2024-01-31 01:33:58 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-31 01:33:58 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-31 01:33:58 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-31 01:33:58 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-31 01:33:58 (4335) [INFO]         compromise:
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-01-31 01:33:58 (4335) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-01-31 01:33:58 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-31 01:33:58 (4352) [INFO] 
* 2024-01-31 01:33:58 (4335) [INFO] Is this ok [y/N]: 
* 2024-01-31 01:33:58 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-31 01:33:58 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-31 01:33:59 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-01-31 01:33:59 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-01-31 01:33:59 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-01-31 01:33:59 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-01-31 01:33:59 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-01-31 01:33:59 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-01-31 01:33:59 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-01-31 01:33:59 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-01-31 01:33:59 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-01-31 01:34:02 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-01-31 01:34:02 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-01-31 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-31 01:34:02 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-01-31 01:34:02 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-01-31 01:34:02 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-31 01:34:02 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EotiFKLNbl/ea_profile.json
* 2024-01-31 01:34:05 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EotiFKLNbl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-31 01:34:05 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-01 01:33:29 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-01 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-01 01:33:29 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-01 01:33:29 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-01 01:33:29 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-01 01:33:29 (4322) [INFO] 
* 2024-02-01 01:33:29 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-01 01:33:30 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 71922.
* 2024-02-01 01:33:30 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:30 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:30 (4335) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-01 01:33:30 (4335) [INFO]     Started: Thu Feb  1 01:33:25 2024 - 00:05 ago
* 2024-02-01 01:33:30 (4335) [INFO]     State  : Sleeping, pid: 71922
* 2024-02-01 01:33:32 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:32 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:32 (4335) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-02-01 01:33:32 (4335) [INFO]     Started: Thu Feb  1 01:33:25 2024 - 00:07 ago
* 2024-02-01 01:33:32 (4335) [INFO]     State  : Sleeping, pid: 71922
* 2024-02-01 01:33:34 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:34 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:34 (4335) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-02-01 01:33:34 (4335) [INFO]     Started: Thu Feb  1 01:33:25 2024 - 00:09 ago
* 2024-02-01 01:33:34 (4335) [INFO]     State  : Sleeping, pid: 71922
* 2024-02-01 01:33:36 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:36 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:36 (4335) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-01 01:33:36 (4335) [INFO]     Started: Thu Feb  1 01:33:25 2024 - 00:11 ago
* 2024-02-01 01:33:36 (4335) [INFO]     State  : Sleeping, pid: 71922
* 2024-02-01 01:33:38 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:38 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:38 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-01 01:33:38 (4335) [INFO]     Started: Thu Feb  1 01:33:25 2024 - 00:13 ago
* 2024-02-01 01:33:38 (4335) [INFO]     State  : Running, pid: 71922
* 2024-02-01 01:33:40 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:40 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:40 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-01 01:33:40 (4335) [INFO]     Started: Thu Feb  1 01:33:25 2024 - 00:15 ago
* 2024-02-01 01:33:40 (4335) [INFO]     State  : Sleeping, pid: 71922
* 2024-02-01 01:33:42 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:42 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:42 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-01 01:33:42 (4335) [INFO]     Started: Thu Feb  1 01:33:25 2024 - 00:17 ago
* 2024-02-01 01:33:42 (4335) [INFO]     State  : Running, pid: 71922
* 2024-02-01 01:33:44 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 72356.
* 2024-02-01 01:33:44 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:44 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:44 (4335) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-01 01:33:44 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:03 ago
* 2024-02-01 01:33:44 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:33:46 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:46 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:46 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:33:46 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:05 ago
* 2024-02-01 01:33:46 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:33:48 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:48 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:48 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:33:48 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:07 ago
* 2024-02-01 01:33:48 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:33:50 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:50 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:50 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:33:50 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:09 ago
* 2024-02-01 01:33:50 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:33:52 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:52 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:52 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:33:52 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:11 ago
* 2024-02-01 01:33:52 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:33:54 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:54 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:54 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:33:54 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:13 ago
* 2024-02-01 01:33:54 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:33:56 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:56 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:56 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:33:56 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:15 ago
* 2024-02-01 01:33:56 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:33:58 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:33:58 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:33:58 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:33:58 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:17 ago
* 2024-02-01 01:33:58 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:34:00 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:34:00 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:34:00 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:34:00 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:19 ago
* 2024-02-01 01:34:00 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:34:02 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 01:34:02 (4335) [INFO]   The other application is: yum
* 2024-02-01 01:34:02 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-01 01:34:02 (4335) [INFO]     Started: Thu Feb  1 01:33:41 2024 - 00:21 ago
* 2024-02-01 01:34:02 (4335) [INFO]     State  : Sleeping, pid: 72356
* 2024-02-01 01:34:04 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-01 01:34:04 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-01 01:34:04 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-01 01:34:04 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-01 01:34:04 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-01 01:34:04 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-01 01:34:04 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-01 01:34:04 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-02-01 01:34:04 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-01 01:34:04 (4352) [INFO] 
* 2024-02-01 01:34:04 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-01 01:34:04 (4322) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-01 01:34:12 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-01 01:34:12 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-01 01:34:12 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-01 01:34:12 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-01 01:34:12 (4335) [INFO] Trying other mirror.
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-01 01:34:12 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-01 01:34:12 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-01 01:34:12 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-01 01:34:12 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-01 01:34:12 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-01 01:34:12 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-01 01:34:12 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-01 01:34:12 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-01 01:34:12 (4335) [INFO]         or
* 2024-02-01 01:34:12 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-01 01:34:12 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-01 01:34:12 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-01 01:34:12 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-01 01:34:12 (4335) [INFO]         compromise:
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-01 01:34:12 (4335) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-01 01:34:12 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-01 01:34:12 (4352) [INFO] 
* 2024-02-01 01:34:12 (4335) [INFO] Is this ok [y/N]: 
* 2024-02-01 01:34:12 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-01 01:34:12 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-01 01:34:13 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-01 01:34:13 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-01 01:34:13 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-01 01:34:13 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-01 01:34:13 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-01 01:34:13 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-01 01:34:13 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-01 01:34:13 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-01 01:34:13 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-01 01:34:18 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-01 01:34:18 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-01 01:34:18 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-01 01:34:18 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-01 01:34:18 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-01 01:34:18 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-01 01:34:18 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0yiEsRQTqe/ea_profile.json
* 2024-02-01 01:34:22 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0yiEsRQTqe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-01 01:34:22 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-02 01:35:17 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-02 01:35:18 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-02 01:35:18 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-02 01:35:18 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-02 01:35:18 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-02 01:35:18 (4322) [INFO] 
* 2024-02-02 01:35:18 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-02 01:35:19 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 534024.
* 2024-02-02 01:35:19 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:19 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:19 (4335) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-02 01:35:19 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:03 ago
* 2024-02-02 01:35:19 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:21 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:21 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:21 (4335) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-02-02 01:35:21 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:05 ago
* 2024-02-02 01:35:21 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:23 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:23 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:23 (4335) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-02 01:35:23 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:07 ago
* 2024-02-02 01:35:23 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:25 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:25 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:25 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-02 01:35:25 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:09 ago
* 2024-02-02 01:35:25 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:27 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:27 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:27 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-02 01:35:27 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:11 ago
* 2024-02-02 01:35:27 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:29 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:29 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:29 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-02 01:35:29 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:13 ago
* 2024-02-02 01:35:29 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:31 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:31 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:31 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-02 01:35:31 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:15 ago
* 2024-02-02 01:35:31 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:33 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:33 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:33 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-02 01:35:33 (4335) [INFO]     Started: Fri Feb  2 01:35:16 2024 - 00:17 ago
* 2024-02-02 01:35:33 (4335) [INFO]     State  : Sleeping, pid: 534024
* 2024-02-02 01:35:35 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 535770.
* 2024-02-02 01:35:35 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:35 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:35 (4335) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-02 01:35:35 (4335) [INFO]     Started: Fri Feb  2 01:35:33 2024 - 00:02 ago
* 2024-02-02 01:35:35 (4335) [INFO]     State  : Sleeping, pid: 535770
* 2024-02-02 01:35:37 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 01:35:37 (4335) [INFO]   The other application is: yum
* 2024-02-02 01:35:37 (4335) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-02 01:35:37 (4335) [INFO]     Started: Fri Feb  2 01:35:33 2024 - 00:04 ago
* 2024-02-02 01:35:37 (4335) [INFO]     State  : Sleeping, pid: 535770
* 2024-02-02 01:35:39 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-02 01:35:39 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-02 01:35:39 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-02 01:35:39 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-02 01:35:39 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-02 01:35:39 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-02 01:35:39 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-02 01:35:39 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-02-02 01:35:39 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-02 01:35:39 (4352) [INFO] 
* 2024-02-02 01:35:39 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-02 01:35:39 (4322) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-02 01:35:47 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-02 01:35:47 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-02 01:35:47 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-02 01:35:47 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-02 01:35:47 (4335) [INFO] Trying other mirror.
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-02 01:35:47 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-02 01:35:47 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-02 01:35:47 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-02 01:35:47 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-02 01:35:47 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-02 01:35:47 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-02 01:35:47 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-02 01:35:47 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-02 01:35:47 (4335) [INFO]         or
* 2024-02-02 01:35:47 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-02 01:35:47 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-02 01:35:47 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-02 01:35:47 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-02 01:35:47 (4335) [INFO]         compromise:
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-02 01:35:47 (4335) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-02 01:35:47 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-02 01:35:47 (4352) [INFO] 
* 2024-02-02 01:35:47 (4335) [INFO] Is this ok [y/N]: 
* 2024-02-02 01:35:47 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-02 01:35:47 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-02 01:35:48 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-02 01:35:48 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-02 01:35:48 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-02 01:35:48 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-02 01:35:48 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-02 01:35:48 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-02 01:35:48 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-02 01:35:48 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-02 01:35:48 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-02 01:35:52 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-02 01:35:52 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-02 01:35:52 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-02 01:35:52 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-02 01:35:52 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-02 01:35:52 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-02 01:35:52 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/128mErG16l/ea_profile.json
* 2024-02-02 01:35:56 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/128mErG16l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-02 01:35:56 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-03 01:36:06 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-03 01:36:06 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-03 01:36:07 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-03 01:36:07 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-03 01:36:07 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-03 01:36:07 (4322) [INFO] 
* 2024-02-03 01:36:07 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-03 01:36:07 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 1001159.
* 2024-02-03 01:36:07 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 01:36:07 (4335) [INFO]   The other application is: yum
* 2024-02-03 01:36:07 (4335) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-03 01:36:07 (4335) [INFO]     Started: Sat Feb  3 01:36:02 2024 - 00:05 ago
* 2024-02-03 01:36:07 (4335) [INFO]     State  : Sleeping, pid: 1001159
* 2024-02-03 01:36:09 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 01:36:09 (4335) [INFO]   The other application is: yum
* 2024-02-03 01:36:09 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-03 01:36:09 (4335) [INFO]     Started: Sat Feb  3 01:36:02 2024 - 00:07 ago
* 2024-02-03 01:36:09 (4335) [INFO]     State  : Sleeping, pid: 1001159
* 2024-02-03 01:36:11 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 01:36:11 (4335) [INFO]   The other application is: yum
* 2024-02-03 01:36:11 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-03 01:36:11 (4335) [INFO]     Started: Sat Feb  3 01:36:02 2024 - 00:09 ago
* 2024-02-03 01:36:11 (4335) [INFO]     State  : Sleeping, pid: 1001159
* 2024-02-03 01:36:13 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 01:36:13 (4335) [INFO]   The other application is: yum
* 2024-02-03 01:36:13 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-03 01:36:13 (4335) [INFO]     Started: Sat Feb  3 01:36:02 2024 - 00:11 ago
* 2024-02-03 01:36:13 (4335) [INFO]     State  : Running, pid: 1001159
* 2024-02-03 01:36:15 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-03 01:36:15 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-03 01:36:15 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-03 01:36:15 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-03 01:36:15 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-03 01:36:15 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-03 01:36:15 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-03 01:36:15 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-02-03 01:36:15 (4335) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-03 01:36:15 (4352) [INFO] 
* 2024-02-03 01:36:15 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-03 01:36:15 (4322) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-03 01:36:22 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-03 01:36:22 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-03 01:36:22 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-03 01:36:22 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-03 01:36:22 (4335) [INFO] Trying other mirror.
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-03 01:36:22 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-03 01:36:22 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-03 01:36:22 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-03 01:36:22 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-03 01:36:22 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-03 01:36:22 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-03 01:36:22 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-03 01:36:22 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-03 01:36:22 (4335) [INFO]         or
* 2024-02-03 01:36:22 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-03 01:36:22 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-03 01:36:22 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-03 01:36:22 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-03 01:36:22 (4335) [INFO]         compromise:
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-03 01:36:22 (4335) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-03 01:36:22 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-03 01:36:22 (4352) [INFO] 
* 2024-02-03 01:36:22 (4335) [INFO] Is this ok [y/N]: 
* 2024-02-03 01:36:22 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-03 01:36:22 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-03 01:36:22 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-03 01:36:23 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-03 01:36:23 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-03 01:36:23 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-03 01:36:23 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-03 01:36:23 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-03 01:36:23 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-03 01:36:23 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-03 01:36:23 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-03 01:36:25 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-03 01:36:25 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-03 01:36:25 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-03 01:36:25 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-03 01:36:25 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-03 01:36:25 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-03 01:36:25 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Qa3l7G4uJz/ea_profile.json
* 2024-02-03 01:36:28 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Qa3l7G4uJz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-03 01:36:28 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-04 01:34:40 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-04 01:34:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-04 01:34:41 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-04 01:34:41 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-04 01:34:41 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-04 01:34:41 (4322) [INFO] 
* 2024-02-04 01:34:41 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-04 01:34:41 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 445892.
* 2024-02-04 01:34:41 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:41 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:41 (4335) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-04 01:34:41 (4335) [INFO]     Started: Sun Feb  4 01:34:37 2024 - 00:04 ago
* 2024-02-04 01:34:41 (4335) [INFO]     State  : Sleeping, pid: 445892
* 2024-02-04 01:34:43 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:43 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:43 (4335) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-04 01:34:43 (4335) [INFO]     Started: Sun Feb  4 01:34:37 2024 - 00:06 ago
* 2024-02-04 01:34:43 (4335) [INFO]     State  : Sleeping, pid: 445892
* 2024-02-04 01:34:45 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:45 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:45 (4335) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-02-04 01:34:45 (4335) [INFO]     Started: Sun Feb  4 01:34:37 2024 - 00:08 ago
* 2024-02-04 01:34:45 (4335) [INFO]     State  : Sleeping, pid: 445892
* 2024-02-04 01:34:47 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:47 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:47 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-04 01:34:47 (4335) [INFO]     Started: Sun Feb  4 01:34:37 2024 - 00:10 ago
* 2024-02-04 01:34:47 (4335) [INFO]     State  : Sleeping, pid: 445892
* 2024-02-04 01:34:49 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:49 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:49 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-04 01:34:49 (4335) [INFO]     Started: Sun Feb  4 01:34:37 2024 - 00:12 ago
* 2024-02-04 01:34:49 (4335) [INFO]     State  : Sleeping, pid: 445892
* 2024-02-04 01:34:51 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:51 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:51 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-04 01:34:51 (4335) [INFO]     Started: Sun Feb  4 01:34:37 2024 - 00:14 ago
* 2024-02-04 01:34:51 (4335) [INFO]     State  : Sleeping, pid: 445892
* 2024-02-04 01:34:53 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 446417.
* 2024-02-04 01:34:53 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:53 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:53 (4335) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-04 01:34:53 (4335) [INFO]     Started: Sun Feb  4 01:34:51 2024 - 00:02 ago
* 2024-02-04 01:34:53 (4335) [INFO]     State  : Sleeping, pid: 446417
* 2024-02-04 01:34:55 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 01:34:55 (4335) [INFO]   The other application is: yum
* 2024-02-04 01:34:55 (4335) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-04 01:34:55 (4335) [INFO]     Started: Sun Feb  4 01:34:51 2024 - 00:04 ago
* 2024-02-04 01:34:55 (4335) [INFO]     State  : Sleeping, pid: 446417
* 2024-02-04 01:34:57 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-04 01:34:57 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-04 01:34:57 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-04 01:34:57 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-04 01:34:57 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-04 01:34:57 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-04 01:34:57 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-04 01:34:57 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-02-04 01:34:57 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-04 01:34:57 (4352) [INFO] 
* 2024-02-04 01:34:57 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-04 01:34:57 (4322) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-04 01:35:04 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-04 01:35:04 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-04 01:35:04 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-04 01:35:04 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-04 01:35:04 (4335) [INFO] Trying other mirror.
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-04 01:35:04 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-04 01:35:04 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-04 01:35:04 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-04 01:35:04 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-04 01:35:04 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-04 01:35:04 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-04 01:35:04 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-04 01:35:04 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-04 01:35:04 (4335) [INFO]         or
* 2024-02-04 01:35:04 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-04 01:35:04 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-04 01:35:04 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-04 01:35:04 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-04 01:35:04 (4335) [INFO]         compromise:
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-04 01:35:04 (4335) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-04 01:35:04 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-04 01:35:04 (4352) [INFO] 
* 2024-02-04 01:35:04 (4335) [INFO] Is this ok [y/N]: 
* 2024-02-04 01:35:04 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-04 01:35:04 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-04 01:35:07 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-04 01:35:07 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-04 01:35:07 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-04 01:35:07 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-04 01:35:07 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-04 01:35:07 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-04 01:35:07 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-04 01:35:07 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-04 01:35:07 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-04 01:35:11 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-04 01:35:11 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-04 01:35:11 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-04 01:35:11 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-04 01:35:11 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-04 01:35:11 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-04 01:35:11 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hG5UshSEjx/ea_profile.json
* 2024-02-04 01:35:15 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hG5UshSEjx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-04 01:35:15 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-05 01:33:42 (161) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-05 01:33:43 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-05 01:33:45 (161) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-05 01:33:45 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-05 01:33:45 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-05 01:33:45 (4322) [INFO] 
* 2024-02-05 01:33:45 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-05 01:33:45 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 896055.
* 2024-02-05 01:33:45 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 01:33:45 (4335) [INFO]   The other application is: yum
* 2024-02-05 01:33:45 (4335) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-05 01:33:45 (4335) [INFO]     Started: Mon Feb  5 01:33:39 2024 - 00:06 ago
* 2024-02-05 01:33:45 (4335) [INFO]     State  : Sleeping, pid: 896055
* 2024-02-05 01:33:47 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 01:33:47 (4335) [INFO]   The other application is: yum
* 2024-02-05 01:33:47 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-05 01:33:47 (4335) [INFO]     Started: Mon Feb  5 01:33:39 2024 - 00:08 ago
* 2024-02-05 01:33:47 (4335) [INFO]     State  : Sleeping, pid: 896055
* 2024-02-05 01:33:49 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 01:33:49 (4335) [INFO]   The other application is: yum
* 2024-02-05 01:33:49 (4335) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-05 01:33:49 (4335) [INFO]     Started: Mon Feb  5 01:33:39 2024 - 00:10 ago
* 2024-02-05 01:33:49 (4335) [INFO]     State  : Sleeping, pid: 896055
* 2024-02-05 01:33:51 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 01:33:51 (4335) [INFO]   The other application is: yum
* 2024-02-05 01:33:51 (4335) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-05 01:33:51 (4335) [INFO]     Started: Mon Feb  5 01:33:39 2024 - 00:12 ago
* 2024-02-05 01:33:51 (4335) [INFO]     State  : Sleeping, pid: 896055
* 2024-02-05 01:33:53 (4335) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 896547.
* 2024-02-05 01:33:53 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 01:33:53 (4335) [INFO]   The other application is: yum
* 2024-02-05 01:33:53 (4335) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-02-05 01:33:53 (4335) [INFO]     Started: Mon Feb  5 01:33:51 2024 - 00:02 ago
* 2024-02-05 01:33:53 (4335) [INFO]     State  : Sleeping, pid: 896547
* 2024-02-05 01:33:55 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 01:33:55 (4335) [INFO]   The other application is: yum
* 2024-02-05 01:33:55 (4335) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-05 01:33:55 (4335) [INFO]     Started: Mon Feb  5 01:33:51 2024 - 00:04 ago
* 2024-02-05 01:33:55 (4335) [INFO]     State  : Sleeping, pid: 896547
* 2024-02-05 01:33:57 (4335) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 01:33:57 (4335) [INFO]   The other application is: yum
* 2024-02-05 01:33:57 (4335) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-05 01:33:57 (4335) [INFO]     Started: Mon Feb  5 01:33:51 2024 - 00:06 ago
* 2024-02-05 01:33:57 (4335) [INFO]     State  : Running, pid: 896547
* 2024-02-05 01:33:59 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-05 01:33:59 (4335) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-05 01:33:59 (4335) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-05 01:33:59 (4335) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-05 01:33:59 (4335) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-05 01:33:59 (4335) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-05 01:33:59 (4335) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-05 01:33:59 (4335) [INFO] Cleaning up list of fastest mirrors
* 2024-02-05 01:33:59 (4335) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-05 01:33:59 (4352) [INFO] 
* 2024-02-05 01:33:59 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-05 01:33:59 (4322) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-05 01:34:07 (4335) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-05 01:34:07 (4335) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-05 01:34:07 (4335) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-05 01:34:07 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-05 01:34:07 (4335) [INFO] Trying other mirror.
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-05 01:34:07 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-05 01:34:07 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-05 01:34:07 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-05 01:34:07 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-05 01:34:07 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-05 01:34:07 (4335) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-05 01:34:07 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-05 01:34:07 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-05 01:34:07 (4335) [INFO]         or
* 2024-02-05 01:34:07 (4335) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-05 01:34:07 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-05 01:34:07 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-05 01:34:07 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-05 01:34:07 (4335) [INFO]         compromise:
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-05 01:34:07 (4335) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-05 01:34:07 (4335) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-05 01:34:07 (4352) [INFO] 
* 2024-02-05 01:34:07 (4335) [INFO] Is this ok [y/N]: 
* 2024-02-05 01:34:07 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-05 01:34:07 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-05 01:34:09 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-05 01:34:09 (1778) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-05 01:34:09 (1778) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-05 01:34:09 (1761) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-05 01:34:09 (1761) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-05 01:34:09 (1778) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-05 01:34:09 (1778) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-05 01:34:09 (1761) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-05 01:34:09 (1778) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-05 01:34:14 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-05 01:34:14 (1702) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-05 01:34:14 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-05 01:34:14 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-05 01:34:14 (161) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-05 01:34:15 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-05 01:34:15 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jggjvWRTV_/ea_profile.json
* 2024-02-05 01:34:19 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jggjvWRTV_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-05 01:34:19 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-06 01:33:34 (162) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-06 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-06 01:33:35 (162) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-06 01:33:35 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-06 01:33:35 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-06 01:33:35 (4416) [INFO] 
* 2024-02-06 01:33:35 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-06 01:33:35 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 297996.
* 2024-02-06 01:33:35 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:35 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:35 (4429) [INFO]     Memory :  38 M RSS (3.0 GB VSZ)
* 2024-02-06 01:33:35 (4429) [INFO]     Started: Tue Feb  6 01:33:31 2024 - 00:04 ago
* 2024-02-06 01:33:35 (4429) [INFO]     State  : Sleeping, pid: 297996
* 2024-02-06 01:33:37 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:37 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:37 (4429) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-06 01:33:37 (4429) [INFO]     Started: Tue Feb  6 01:33:31 2024 - 00:06 ago
* 2024-02-06 01:33:37 (4429) [INFO]     State  : Sleeping, pid: 297996
* 2024-02-06 01:33:39 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:39 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:39 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-06 01:33:39 (4429) [INFO]     Started: Tue Feb  6 01:33:31 2024 - 00:08 ago
* 2024-02-06 01:33:39 (4429) [INFO]     State  : Sleeping, pid: 297996
* 2024-02-06 01:33:41 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:41 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:41 (4429) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-06 01:33:41 (4429) [INFO]     Started: Tue Feb  6 01:33:31 2024 - 00:10 ago
* 2024-02-06 01:33:41 (4429) [INFO]     State  : Sleeping, pid: 297996
* 2024-02-06 01:33:43 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:43 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:43 (4429) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-06 01:33:43 (4429) [INFO]     Started: Tue Feb  6 01:33:31 2024 - 00:12 ago
* 2024-02-06 01:33:43 (4429) [INFO]     State  : Sleeping, pid: 297996
* 2024-02-06 01:33:45 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:45 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:45 (4429) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-06 01:33:45 (4429) [INFO]     Started: Tue Feb  6 01:33:31 2024 - 00:14 ago
* 2024-02-06 01:33:45 (4429) [INFO]     State  : Sleeping, pid: 297996
* 2024-02-06 01:33:47 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 298408.
* 2024-02-06 01:33:47 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:47 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:47 (4429) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-06 01:33:47 (4429) [INFO]     Started: Tue Feb  6 01:33:45 2024 - 00:02 ago
* 2024-02-06 01:33:47 (4429) [INFO]     State  : Sleeping, pid: 298408
* 2024-02-06 01:33:49 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:49 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:49 (4429) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-06 01:33:49 (4429) [INFO]     Started: Tue Feb  6 01:33:45 2024 - 00:04 ago
* 2024-02-06 01:33:49 (4429) [INFO]     State  : Sleeping, pid: 298408
* 2024-02-06 01:33:51 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 01:33:51 (4429) [INFO]   The other application is: yum
* 2024-02-06 01:33:51 (4429) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-06 01:33:51 (4429) [INFO]     Started: Tue Feb  6 01:33:45 2024 - 00:06 ago
* 2024-02-06 01:33:51 (4429) [INFO]     State  : Sleeping, pid: 298408
* 2024-02-06 01:33:53 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-06 01:33:53 (4429) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-06 01:33:53 (4429) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-06 01:33:53 (4429) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-06 01:33:53 (4429) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-06 01:33:53 (4429) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-06 01:33:53 (4429) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-06 01:33:53 (4429) [INFO] Cleaning up list of fastest mirrors
* 2024-02-06 01:33:53 (4429) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-06 01:33:53 (4446) [INFO] 
* 2024-02-06 01:33:53 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-06 01:33:53 (4416) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-06 01:34:01 (4429) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-06 01:34:01 (4429) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-06 01:34:01 (4429) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-06 01:34:01 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-06 01:34:01 (4429) [INFO] Trying other mirror.
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-06 01:34:01 (4429) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-06 01:34:01 (4429) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-06 01:34:01 (4429) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-06 01:34:01 (4429) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-06 01:34:01 (4429) [INFO]         packages for the previous distribution release still work).
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-06 01:34:01 (4429) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-06 01:34:01 (4429) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-06 01:34:01 (4429) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-06 01:34:01 (4429) [INFO]         or
* 2024-02-06 01:34:01 (4429) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-06 01:34:01 (4429) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-06 01:34:01 (4429) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-06 01:34:01 (4429) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-06 01:34:01 (4429) [INFO]         compromise:
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-06 01:34:01 (4429) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-06 01:34:01 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-06 01:34:01 (4446) [INFO] 
* 2024-02-06 01:34:01 (4429) [INFO] Is this ok [y/N]: 
* 2024-02-06 01:34:01 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-06 01:34:01 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-06 01:34:02 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-06 01:34:02 (1780) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-06 01:34:02 (1780) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-06 01:34:02 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-06 01:34:02 (1763) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-06 01:34:02 (1780) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-06 01:34:02 (1780) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-06 01:34:02 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-06 01:34:02 (1780) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-06 01:34:08 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-06 01:34:08 (1704) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-06 01:34:08 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-06 01:34:09 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-06 01:34:09 (162) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-06 01:34:09 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-06 01:34:09 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mdx5HXiQtc/ea_profile.json
* 2024-02-06 01:34:42 (309) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mdx5HXiQtc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-06 01:34:42 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-07 01:33:37 (162) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-07 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-07 01:33:38 (162) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-07 01:33:38 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-07 01:33:38 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-07 01:33:38 (4416) [INFO] 
* 2024-02-07 01:33:38 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-07 01:33:38 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 19534.
* 2024-02-07 01:33:38 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 01:33:38 (4429) [INFO]   The other application is: yum
* 2024-02-07 01:33:38 (4429) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-07 01:33:38 (4429) [INFO]     Started: Wed Feb  7 01:33:34 2024 - 00:04 ago
* 2024-02-07 01:33:38 (4429) [INFO]     State  : Sleeping, pid: 19534
* 2024-02-07 01:33:40 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 01:33:40 (4429) [INFO]   The other application is: yum
* 2024-02-07 01:33:40 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-07 01:33:40 (4429) [INFO]     Started: Wed Feb  7 01:33:34 2024 - 00:06 ago
* 2024-02-07 01:33:40 (4429) [INFO]     State  : Sleeping, pid: 19534
* 2024-02-07 01:33:42 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 01:33:42 (4429) [INFO]   The other application is: yum
* 2024-02-07 01:33:42 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-07 01:33:42 (4429) [INFO]     Started: Wed Feb  7 01:33:34 2024 - 00:08 ago
* 2024-02-07 01:33:42 (4429) [INFO]     State  : Sleeping, pid: 19534
* 2024-02-07 01:33:44 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-07 01:33:44 (4429) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-07 01:33:44 (4429) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-07 01:33:44 (4429) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-07 01:33:44 (4429) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-07 01:33:44 (4429) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-07 01:33:44 (4429) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-07 01:33:44 (4429) [INFO] Cleaning up list of fastest mirrors
* 2024-02-07 01:33:44 (4429) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-07 01:33:44 (4446) [INFO] 
* 2024-02-07 01:33:44 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-07 01:33:44 (4416) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-07 01:33:53 (4429) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-07 01:33:53 (4429) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-07 01:33:53 (4429) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-07 01:33:53 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-07 01:33:53 (4429) [INFO] Trying other mirror.
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-07 01:33:53 (4429) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-07 01:33:53 (4429) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-07 01:33:53 (4429) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-07 01:33:53 (4429) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-07 01:33:53 (4429) [INFO]         packages for the previous distribution release still work).
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-07 01:33:53 (4429) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-07 01:33:53 (4429) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-07 01:33:53 (4429) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-07 01:33:53 (4429) [INFO]         or
* 2024-02-07 01:33:53 (4429) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-07 01:33:53 (4429) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-07 01:33:53 (4429) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-07 01:33:53 (4429) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-07 01:33:53 (4429) [INFO]         compromise:
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-07 01:33:53 (4429) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-07 01:33:53 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-07 01:33:53 (4446) [INFO] 
* 2024-02-07 01:33:53 (4429) [INFO] Is this ok [y/N]: 
* 2024-02-07 01:33:53 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-07 01:33:53 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-07 01:33:56 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-07 01:33:56 (1780) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-07 01:33:56 (1780) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-07 01:33:56 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-07 01:33:56 (1763) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-07 01:33:56 (1780) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-07 01:33:56 (1780) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-07 01:33:56 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-07 01:33:56 (1780) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-07 01:34:00 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-07 01:34:00 (1704) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-07 01:34:00 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-07 01:34:00 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-07 01:34:00 (162) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-07 01:34:00 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-07 01:34:01 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QdSkNWWqFm/ea_profile.json
* 2024-02-07 01:34:07 (309) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QdSkNWWqFm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-07 01:34:07 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-08 01:33:35 (162) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-08 01:33:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-08 01:33:36 (162) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-08 01:33:36 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-08 01:33:36 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-08 01:33:36 (4416) [INFO] 
* 2024-02-08 01:33:37 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-08 01:33:37 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 7635.
* 2024-02-08 01:33:37 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-08 01:33:37 (4429) [INFO]   The other application is: yum
* 2024-02-08 01:33:37 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-08 01:33:37 (4429) [INFO]     Started: Thu Feb  8 01:33:32 2024 - 00:05 ago
* 2024-02-08 01:33:37 (4429) [INFO]     State  : Sleeping, pid: 7635
* 2024-02-08 01:33:39 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-08 01:33:39 (4429) [INFO]   The other application is: yum
* 2024-02-08 01:33:39 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-08 01:33:39 (4429) [INFO]     Started: Thu Feb  8 01:33:32 2024 - 00:07 ago
* 2024-02-08 01:33:39 (4429) [INFO]     State  : Sleeping, pid: 7635
* 2024-02-08 01:33:41 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-08 01:33:41 (4429) [INFO]   The other application is: yum
* 2024-02-08 01:33:41 (4429) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-08 01:33:41 (4429) [INFO]     Started: Thu Feb  8 01:33:32 2024 - 00:09 ago
* 2024-02-08 01:33:41 (4429) [INFO]     State  : Sleeping, pid: 7635
* 2024-02-08 01:33:43 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-08 01:33:43 (4429) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-08 01:33:43 (4429) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-08 01:33:43 (4429) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-08 01:33:43 (4429) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-08 01:33:43 (4429) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-08 01:33:43 (4429) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-08 01:33:43 (4429) [INFO] Cleaning up list of fastest mirrors
* 2024-02-08 01:33:43 (4429) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-08 01:33:43 (4446) [INFO] 
* 2024-02-08 01:33:43 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-08 01:33:43 (4416) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-08 01:34:01 (4429) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-08 01:34:01 (4429) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-08 01:34:01 (4429) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-08 01:34:01 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-08 01:34:01 (4429) [INFO] Trying other mirror.
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-08 01:34:01 (4429) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-08 01:34:01 (4429) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-08 01:34:01 (4429) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-08 01:34:01 (4429) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-08 01:34:01 (4429) [INFO]         packages for the previous distribution release still work).
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-08 01:34:01 (4429) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-08 01:34:01 (4429) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-08 01:34:01 (4429) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-08 01:34:01 (4429) [INFO]         or
* 2024-02-08 01:34:01 (4429) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-08 01:34:01 (4429) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-08 01:34:01 (4429) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-08 01:34:01 (4429) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-08 01:34:01 (4429) [INFO]         compromise:
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-08 01:34:01 (4429) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-08 01:34:01 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-08 01:34:01 (4446) [INFO] 
* 2024-02-08 01:34:01 (4429) [INFO] Is this ok [y/N]: 
* 2024-02-08 01:34:01 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-08 01:34:01 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-08 01:34:07 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-08 01:34:07 (1780) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-08 01:34:07 (1780) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-08 01:34:07 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-08 01:34:07 (1763) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-08 01:34:07 (1780) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-08 01:34:07 (1780) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-08 01:34:07 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-08 01:34:07 (1780) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-08 01:34:21 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-08 01:34:21 (1704) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-08 01:34:21 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-08 01:34:21 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-08 01:34:21 (162) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-08 01:34:22 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-08 01:34:22 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oNaYQSn0BR/ea_profile.json
* 2024-02-08 01:34:30 (309) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oNaYQSn0BR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-08 01:34:30 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-09 01:33:41 (162) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-09 01:33:41 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-09 01:33:42 (162) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-09 01:33:42 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-09 01:33:42 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-09 01:33:42 (4416) [INFO] 
* 2024-02-09 01:33:42 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-09 01:33:42 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 24833.
* 2024-02-09 01:33:42 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-09 01:33:42 (4429) [INFO]   The other application is: yum
* 2024-02-09 01:33:42 (4429) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-09 01:33:42 (4429) [INFO]     Started: Fri Feb  9 01:33:37 2024 - 00:05 ago
* 2024-02-09 01:33:42 (4429) [INFO]     State  : Sleeping, pid: 24833
* 2024-02-09 01:33:44 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-09 01:33:44 (4429) [INFO]   The other application is: yum
* 2024-02-09 01:33:44 (4429) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-09 01:33:44 (4429) [INFO]     Started: Fri Feb  9 01:33:37 2024 - 00:07 ago
* 2024-02-09 01:33:44 (4429) [INFO]     State  : Sleeping, pid: 24833
* 2024-02-09 01:33:46 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-09 01:33:46 (4429) [INFO]   The other application is: yum
* 2024-02-09 01:33:46 (4429) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-09 01:33:46 (4429) [INFO]     Started: Fri Feb  9 01:33:37 2024 - 00:09 ago
* 2024-02-09 01:33:46 (4429) [INFO]     State  : Sleeping, pid: 24833
* 2024-02-09 01:33:48 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 25247.
* 2024-02-09 01:33:48 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-09 01:33:48 (4429) [INFO]   The other application is: yum
* 2024-02-09 01:33:48 (4429) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-09 01:33:48 (4429) [INFO]     Started: Fri Feb  9 01:33:45 2024 - 00:03 ago
* 2024-02-09 01:33:48 (4429) [INFO]     State  : Sleeping, pid: 25247
* 2024-02-09 01:33:50 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-09 01:33:50 (4429) [INFO]   The other application is: yum
* 2024-02-09 01:33:50 (4429) [INFO]     Memory :  38 M RSS (333 MB VSZ)
* 2024-02-09 01:33:50 (4429) [INFO]     Started: Fri Feb  9 01:33:45 2024 - 00:05 ago
* 2024-02-09 01:33:50 (4429) [INFO]     State  : Sleeping, pid: 25247
* 2024-02-09 01:33:52 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-09 01:33:52 (4429) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-09 01:33:52 (4429) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-09 01:33:52 (4429) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-09 01:33:52 (4429) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-09 01:33:52 (4429) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-09 01:33:52 (4429) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-09 01:33:52 (4429) [INFO] Cleaning up list of fastest mirrors
* 2024-02-09 01:33:52 (4429) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-09 01:33:52 (4446) [INFO] 
* 2024-02-09 01:33:52 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-09 01:33:52 (4416) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-09 01:34:00 (4429) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-09 01:34:00 (4429) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-09 01:34:00 (4429) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-09 01:34:00 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-09 01:34:00 (4429) [INFO] Trying other mirror.
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-09 01:34:00 (4429) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-09 01:34:00 (4429) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-09 01:34:00 (4429) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-09 01:34:00 (4429) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-09 01:34:00 (4429) [INFO]         packages for the previous distribution release still work).
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-09 01:34:00 (4429) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-09 01:34:00 (4429) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-09 01:34:00 (4429) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-09 01:34:00 (4429) [INFO]         or
* 2024-02-09 01:34:00 (4429) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-09 01:34:00 (4429) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-09 01:34:00 (4429) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-09 01:34:00 (4429) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-09 01:34:00 (4429) [INFO]         compromise:
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-09 01:34:00 (4429) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-09 01:34:00 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-09 01:34:00 (4446) [INFO] 
* 2024-02-09 01:34:00 (4429) [INFO] Is this ok [y/N]: 
* 2024-02-09 01:34:00 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-09 01:34:00 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-09 01:34:03 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-09 01:34:03 (1780) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-09 01:34:03 (1780) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-09 01:34:03 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-09 01:34:03 (1763) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-09 01:34:03 (1780) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-09 01:34:03 (1780) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-09 01:34:03 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-09 01:34:03 (1780) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-09 01:34:09 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-09 01:34:09 (1704) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-09 01:34:09 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-09 01:34:09 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-09 01:34:09 (162) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-09 01:34:09 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-09 01:34:09 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tpG1F2LItR/ea_profile.json
* 2024-02-09 01:34:13 (309) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tpG1F2LItR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-09 01:34:13 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-10 01:34:53 (162) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-10 01:34:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-10 01:34:54 (162) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-10 01:34:54 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-10 01:34:54 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-10 01:34:54 (4416) [INFO] 
* 2024-02-10 01:34:54 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-10 01:34:54 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 32360.
* 2024-02-10 01:34:54 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-10 01:34:54 (4429) [INFO]   The other application is: yum
* 2024-02-10 01:34:54 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-10 01:34:54 (4429) [INFO]     Started: Sat Feb 10 01:34:50 2024 - 00:04 ago
* 2024-02-10 01:34:54 (4429) [INFO]     State  : Sleeping, pid: 32360
* 2024-02-10 01:34:56 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-10 01:34:56 (4429) [INFO]   The other application is: yum
* 2024-02-10 01:34:56 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-10 01:34:56 (4429) [INFO]     Started: Sat Feb 10 01:34:50 2024 - 00:06 ago
* 2024-02-10 01:34:56 (4429) [INFO]     State  : Sleeping, pid: 32360
* 2024-02-10 01:34:58 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-10 01:34:58 (4429) [INFO]   The other application is: yum
* 2024-02-10 01:34:58 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-10 01:34:58 (4429) [INFO]     Started: Sat Feb 10 01:34:50 2024 - 00:08 ago
* 2024-02-10 01:34:58 (4429) [INFO]     State  : Sleeping, pid: 32360
* 2024-02-10 01:35:00 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-10 01:35:00 (4429) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-10 01:35:00 (4429) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-10 01:35:00 (4429) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-10 01:35:00 (4429) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-10 01:35:00 (4429) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-10 01:35:00 (4429) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-10 01:35:00 (4429) [INFO] Cleaning up list of fastest mirrors
* 2024-02-10 01:35:00 (4429) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-10 01:35:00 (4446) [INFO] 
* 2024-02-10 01:35:00 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-10 01:35:00 (4416) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-10 01:35:09 (4429) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-10 01:35:09 (4429) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-10 01:35:09 (4429) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-10 01:35:09 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-10 01:35:09 (4429) [INFO] Trying other mirror.
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-10 01:35:09 (4429) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-10 01:35:09 (4429) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-10 01:35:09 (4429) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-10 01:35:09 (4429) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-10 01:35:09 (4429) [INFO]         packages for the previous distribution release still work).
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-10 01:35:09 (4429) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-10 01:35:09 (4429) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-10 01:35:09 (4429) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-10 01:35:09 (4429) [INFO]         or
* 2024-02-10 01:35:09 (4429) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-10 01:35:09 (4429) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-10 01:35:09 (4429) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-10 01:35:09 (4429) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-10 01:35:09 (4429) [INFO]         compromise:
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-10 01:35:09 (4429) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-10 01:35:09 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-10 01:35:09 (4446) [INFO] 
* 2024-02-10 01:35:09 (4429) [INFO] Is this ok [y/N]: 
* 2024-02-10 01:35:09 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-10 01:35:09 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-10 01:35:14 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-10 01:35:14 (1780) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-10 01:35:14 (1780) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-10 01:35:14 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-10 01:35:14 (1763) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-10 01:35:14 (1780) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-10 01:35:14 (1780) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-10 01:35:14 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-10 01:35:14 (1780) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-10 01:35:22 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-10 01:35:22 (1704) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 350.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  34 M RSS (325 MB VSZ)
    Started: Sat Feb 10 01:34:59 2024 - 00:16 ago
    State  : Sleeping, pid: 350
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Sat Feb 10 01:34:59 2024 - 00:18 ago
    State  : Sleeping, pid: 350
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-10 01:35:22 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-10 01:35:22 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-10 01:35:22 (162) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-10 01:35:22 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-10 01:35:22 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/20WinSRphS/ea_profile.json
* 2024-02-10 01:35:26 (309) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/20WinSRphS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-10 01:35:26 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-11 01:35:02 (162) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-11 01:35:02 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-11 01:35:03 (162) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-11 01:35:03 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-11 01:35:03 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-11 01:35:03 (4416) [INFO] 
* 2024-02-11 01:35:03 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-11 01:35:03 (4429) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 27076.
* 2024-02-11 01:35:03 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-11 01:35:03 (4429) [INFO]   The other application is: yum
* 2024-02-11 01:35:03 (4429) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-02-11 01:35:03 (4429) [INFO]     Started: Sun Feb 11 01:34:59 2024 - 00:04 ago
* 2024-02-11 01:35:03 (4429) [INFO]     State  : Sleeping, pid: 27076
* 2024-02-11 01:35:05 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-11 01:35:05 (4429) [INFO]   The other application is: yum
* 2024-02-11 01:35:05 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-11 01:35:05 (4429) [INFO]     Started: Sun Feb 11 01:34:59 2024 - 00:06 ago
* 2024-02-11 01:35:05 (4429) [INFO]     State  : Uninterruptible, pid: 27076
* 2024-02-11 01:35:07 (4429) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-11 01:35:07 (4429) [INFO]   The other application is: yum
* 2024-02-11 01:35:07 (4429) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-11 01:35:07 (4429) [INFO]     Started: Sun Feb 11 01:34:59 2024 - 00:08 ago
* 2024-02-11 01:35:07 (4429) [INFO]     State  : Sleeping, pid: 27076
* 2024-02-11 01:35:09 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-11 01:35:09 (4429) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-11 01:35:09 (4429) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-11 01:35:09 (4429) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-11 01:35:09 (4429) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-11 01:35:09 (4429) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-11 01:35:09 (4429) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-11 01:35:09 (4429) [INFO] Cleaning up list of fastest mirrors
* 2024-02-11 01:35:09 (4429) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-11 01:35:09 (4446) [INFO] 
* 2024-02-11 01:35:09 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-11 01:35:09 (4416) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-11 01:35:17 (4429) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-11 01:35:17 (4429) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-11 01:35:17 (4429) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-11 01:35:17 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-11 01:35:17 (4429) [INFO] Trying other mirror.
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-11 01:35:17 (4429) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-11 01:35:17 (4429) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-11 01:35:17 (4429) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-11 01:35:17 (4429) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-11 01:35:17 (4429) [INFO]         packages for the previous distribution release still work).
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-11 01:35:17 (4429) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-11 01:35:17 (4429) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-11 01:35:17 (4429) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-11 01:35:17 (4429) [INFO]         or
* 2024-02-11 01:35:17 (4429) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-11 01:35:17 (4429) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-11 01:35:17 (4429) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-11 01:35:17 (4429) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-11 01:35:17 (4429) [INFO]         compromise:
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-11 01:35:17 (4429) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-11 01:35:17 (4429) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-11 01:35:17 (4446) [INFO] 
* 2024-02-11 01:35:17 (4429) [INFO] Is this ok [y/N]: 
* 2024-02-11 01:35:17 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-11 01:35:17 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-11 01:35:21 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-11 01:35:21 (1780) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-11 01:35:21 (1780) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-11 01:35:21 (1763) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-11 01:35:21 (1763) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-11 01:35:21 (1780) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-11 01:35:21 (1780) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-11 01:35:21 (1763) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-11 01:35:21 (1780) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-11 01:35:26 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-11 01:35:26 (1704) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-11 01:35:26 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-11 01:35:26 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password".
Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.
* 2024-02-11 01:35:26 (162) [WARN] *** Elevation Blocker detected: ***
Issue with sshd configuration
* 2024-02-11 01:35:26 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-11 01:35:26 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qUMVfo7w_H/ea_profile.json
* 2024-02-11 01:35:28 (309) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qUMVfo7w_H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-11 01:35:28 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-13 01:33:28 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-13 01:33:28 (1912) [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-02-13 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-13 01:33:28 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-13 01:33:28 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-13 01:33:28 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-13 01:33:28 (4463) [INFO] 
* 2024-02-13 01:33:28 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-13 01:33:29 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 21799.
* 2024-02-13 01:33:29 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-13 01:33:29 (4476) [INFO]   The other application is: yum
* 2024-02-13 01:33:29 (4476) [INFO]     Memory :  38 M RSS (2.9 GB VSZ)
* 2024-02-13 01:33:29 (4476) [INFO]     Started: Tue Feb 13 01:33:25 2024 - 00:04 ago
* 2024-02-13 01:33:29 (4476) [INFO]     State  : Sleeping, pid: 21799
* 2024-02-13 01:33:31 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-13 01:33:31 (4476) [INFO]   The other application is: yum
* 2024-02-13 01:33:31 (4476) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-13 01:33:31 (4476) [INFO]     Started: Tue Feb 13 01:33:25 2024 - 00:06 ago
* 2024-02-13 01:33:31 (4476) [INFO]     State  : Sleeping, pid: 21799
* 2024-02-13 01:33:33 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-13 01:33:33 (4476) [INFO]   The other application is: yum
* 2024-02-13 01:33:33 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-13 01:33:33 (4476) [INFO]     Started: Tue Feb 13 01:33:25 2024 - 00:08 ago
* 2024-02-13 01:33:33 (4476) [INFO]     State  : Sleeping, pid: 21799
* 2024-02-13 01:33:35 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-13 01:33:35 (4476) [INFO]   The other application is: yum
* 2024-02-13 01:33:35 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-13 01:33:35 (4476) [INFO]     Started: Tue Feb 13 01:33:25 2024 - 00:10 ago
* 2024-02-13 01:33:35 (4476) [INFO]     State  : Sleeping, pid: 21799
* 2024-02-13 01:33:37 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 22158.
* 2024-02-13 01:33:37 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-13 01:33:37 (4476) [INFO]   The other application is: yum
* 2024-02-13 01:33:37 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-13 01:33:37 (4476) [INFO]     Started: Tue Feb 13 01:33:34 2024 - 00:03 ago
* 2024-02-13 01:33:37 (4476) [INFO]     State  : Sleeping, pid: 22158
* 2024-02-13 01:33:39 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-13 01:33:39 (4476) [INFO]   The other application is: yum
* 2024-02-13 01:33:39 (4476) [INFO]     Memory :  39 M RSS (332 MB VSZ)
* 2024-02-13 01:33:39 (4476) [INFO]     Started: Tue Feb 13 01:33:34 2024 - 00:05 ago
* 2024-02-13 01:33:39 (4476) [INFO]     State  : Uninterruptible, pid: 22158
* 2024-02-13 01:33:41 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-13 01:33:41 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-13 01:33:41 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-13 01:33:41 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-13 01:33:41 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-13 01:33:41 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-13 01:33:41 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-13 01:33:41 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-13 01:33:41 (4476) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-13 01:33:41 (4493) [INFO] 
* 2024-02-13 01:33:41 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-13 01:33:41 (4463) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-13 01:33:47 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-13 01:33:47 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-13 01:33:47 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-13 01:33:47 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-13 01:33:47 (4476) [INFO] Trying other mirror.
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-13 01:33:47 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-13 01:33:47 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-13 01:33:47 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-13 01:33:47 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-13 01:33:47 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-13 01:33:47 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-13 01:33:47 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-13 01:33:47 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-13 01:33:47 (4476) [INFO]         or
* 2024-02-13 01:33:47 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-13 01:33:47 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-13 01:33:47 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-13 01:33:47 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-13 01:33:47 (4476) [INFO]         compromise:
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-13 01:33:47 (4476) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-13 01:33:47 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-13 01:33:47 (4493) [INFO] 
* 2024-02-13 01:33:47 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-13 01:33:47 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-13 01:33:47 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-13 01:33:48 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-13 01:33:48 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-13 01:33:48 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-13 01:33:48 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-13 01:33:48 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-13 01:33:48 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-13 01:33:48 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-13 01:33:48 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-13 01:33:48 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-13 01:33:52 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-13 01:33:52 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-13 01:33:52 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-13 01:33:52 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-13 01:33:52 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rSAmTStCUQ/ea_profile.json
* 2024-02-13 01:33:56 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rSAmTStCUQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-13 01:33:56 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-14 01:33:44 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-14 01:33:44 (1912) [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-02-14 01:33:44 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-14 01:33:45 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-14 01:33:45 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-14 01:33:45 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-14 01:33:45 (4463) [INFO] 
* 2024-02-14 01:33:45 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-14 01:33:45 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 303699.
* 2024-02-14 01:33:45 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:45 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:45 (4476) [INFO]     Memory :  38 M RSS (2.9 GB VSZ)
* 2024-02-14 01:33:45 (4476) [INFO]     Started: Wed Feb 14 01:33:42 2024 - 00:03 ago
* 2024-02-14 01:33:45 (4476) [INFO]     State  : Sleeping, pid: 303699
* 2024-02-14 01:33:47 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:47 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:47 (4476) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-14 01:33:47 (4476) [INFO]     Started: Wed Feb 14 01:33:42 2024 - 00:05 ago
* 2024-02-14 01:33:47 (4476) [INFO]     State  : Sleeping, pid: 303699
* 2024-02-14 01:33:49 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:49 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:49 (4476) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-14 01:33:49 (4476) [INFO]     Started: Wed Feb 14 01:33:42 2024 - 00:07 ago
* 2024-02-14 01:33:49 (4476) [INFO]     State  : Sleeping, pid: 303699
* 2024-02-14 01:33:51 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:51 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:51 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-14 01:33:51 (4476) [INFO]     Started: Wed Feb 14 01:33:42 2024 - 00:09 ago
* 2024-02-14 01:33:51 (4476) [INFO]     State  : Sleeping, pid: 303699
* 2024-02-14 01:33:53 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:53 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:53 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-14 01:33:53 (4476) [INFO]     Started: Wed Feb 14 01:33:42 2024 - 00:11 ago
* 2024-02-14 01:33:53 (4476) [INFO]     State  : Sleeping, pid: 303699
* 2024-02-14 01:33:55 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:55 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:55 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-14 01:33:55 (4476) [INFO]     Started: Wed Feb 14 01:33:42 2024 - 00:13 ago
* 2024-02-14 01:33:55 (4476) [INFO]     State  : Sleeping, pid: 303699
* 2024-02-14 01:33:57 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 304144.
* 2024-02-14 01:33:57 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:57 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:57 (4476) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-14 01:33:57 (4476) [INFO]     Started: Wed Feb 14 01:33:55 2024 - 00:02 ago
* 2024-02-14 01:33:57 (4476) [INFO]     State  : Sleeping, pid: 304144
* 2024-02-14 01:33:59 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-14 01:33:59 (4476) [INFO]   The other application is: yum
* 2024-02-14 01:33:59 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-14 01:33:59 (4476) [INFO]     Started: Wed Feb 14 01:33:55 2024 - 00:04 ago
* 2024-02-14 01:33:59 (4476) [INFO]     State  : Sleeping, pid: 304144
* 2024-02-14 01:34:01 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-14 01:34:01 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-14 01:34:01 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-14 01:34:01 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-14 01:34:01 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-14 01:34:01 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-14 01:34:01 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-14 01:34:01 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-14 01:34:01 (4476) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-14 01:34:01 (4493) [INFO] 
* 2024-02-14 01:34:01 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-14 01:34:01 (4463) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-14 01:34:08 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-14 01:34:08 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-14 01:34:08 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-14 01:34:08 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-14 01:34:08 (4476) [INFO] Trying other mirror.
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-14 01:34:08 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-14 01:34:08 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-14 01:34:08 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-14 01:34:08 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-14 01:34:08 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-14 01:34:08 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-14 01:34:08 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-14 01:34:08 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-14 01:34:08 (4476) [INFO]         or
* 2024-02-14 01:34:08 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-14 01:34:08 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-14 01:34:08 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-14 01:34:08 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-14 01:34:08 (4476) [INFO]         compromise:
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-14 01:34:08 (4476) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-14 01:34:08 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-14 01:34:08 (4493) [INFO] 
* 2024-02-14 01:34:08 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-14 01:34:08 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-14 01:34:08 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-14 01:34:10 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-14 01:34:10 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-14 01:34:10 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-14 01:34:10 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-14 01:34:10 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-14 01:34:10 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-14 01:34:10 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-14 01:34:10 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-14 01:34:10 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-14 01:34:14 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-14 01:34:14 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-14 01:34:14 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-14 01:34:14 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-14 01:34:14 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7kjig2o3tN/ea_profile.json
* 2024-02-14 01:34:18 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7kjig2o3tN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-14 01:34:18 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-15 01:33:48 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-15 01:33:48 (1912) [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-02-15 01:33:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-15 01:33:49 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-15 01:33:49 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-15 01:33:49 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-15 01:33:49 (4463) [INFO] 
* 2024-02-15 01:33:49 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-15 01:33:50 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 703779.
* 2024-02-15 01:33:50 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:33:50 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:33:50 (4476) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-02-15 01:33:50 (4476) [INFO]     Started: Thu Feb 15 01:33:46 2024 - 00:04 ago
* 2024-02-15 01:33:50 (4476) [INFO]     State  : Sleeping, pid: 703779
* 2024-02-15 01:33:52 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:33:52 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:33:52 (4476) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-15 01:33:52 (4476) [INFO]     Started: Thu Feb 15 01:33:46 2024 - 00:06 ago
* 2024-02-15 01:33:52 (4476) [INFO]     State  : Sleeping, pid: 703779
* 2024-02-15 01:33:54 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:33:54 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:33:54 (4476) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-15 01:33:54 (4476) [INFO]     Started: Thu Feb 15 01:33:46 2024 - 00:08 ago
* 2024-02-15 01:33:54 (4476) [INFO]     State  : Sleeping, pid: 703779
* 2024-02-15 01:33:56 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:33:56 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:33:56 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-15 01:33:56 (4476) [INFO]     Started: Thu Feb 15 01:33:46 2024 - 00:10 ago
* 2024-02-15 01:33:56 (4476) [INFO]     State  : Sleeping, pid: 703779
* 2024-02-15 01:33:58 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:33:58 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:33:58 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-15 01:33:58 (4476) [INFO]     Started: Thu Feb 15 01:33:46 2024 - 00:12 ago
* 2024-02-15 01:33:58 (4476) [INFO]     State  : Sleeping, pid: 703779
* 2024-02-15 01:34:00 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:34:00 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:34:00 (4476) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-15 01:34:00 (4476) [INFO]     Started: Thu Feb 15 01:33:46 2024 - 00:14 ago
* 2024-02-15 01:34:00 (4476) [INFO]     State  : Sleeping, pid: 703779
* 2024-02-15 01:34:02 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 704272.
* 2024-02-15 01:34:02 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:34:02 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:34:02 (4476) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-02-15 01:34:02 (4476) [INFO]     Started: Thu Feb 15 01:34:00 2024 - 00:02 ago
* 2024-02-15 01:34:02 (4476) [INFO]     State  : Sleeping, pid: 704272
* 2024-02-15 01:34:04 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:34:04 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:34:04 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-15 01:34:04 (4476) [INFO]     Started: Thu Feb 15 01:34:00 2024 - 00:04 ago
* 2024-02-15 01:34:04 (4476) [INFO]     State  : Sleeping, pid: 704272
* 2024-02-15 01:34:06 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-15 01:34:06 (4476) [INFO]   The other application is: yum
* 2024-02-15 01:34:06 (4476) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-15 01:34:06 (4476) [INFO]     Started: Thu Feb 15 01:34:00 2024 - 00:06 ago
* 2024-02-15 01:34:06 (4476) [INFO]     State  : Sleeping, pid: 704272
* 2024-02-15 01:34:08 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-15 01:34:08 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-15 01:34:08 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-15 01:34:08 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-15 01:34:08 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-15 01:34:08 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-15 01:34:08 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-15 01:34:08 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-15 01:34:08 (4476) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-15 01:34:08 (4493) [INFO] 
* 2024-02-15 01:34:08 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-15 01:34:08 (4463) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-15 01:34:18 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-15 01:34:18 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-15 01:34:18 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-15 01:34:18 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-15 01:34:18 (4476) [INFO] Trying other mirror.
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-15 01:34:18 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-15 01:34:18 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-15 01:34:18 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-15 01:34:18 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-15 01:34:18 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-15 01:34:18 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-15 01:34:18 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-15 01:34:18 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-15 01:34:18 (4476) [INFO]         or
* 2024-02-15 01:34:18 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-15 01:34:18 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-15 01:34:18 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-15 01:34:18 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-15 01:34:18 (4476) [INFO]         compromise:
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-15 01:34:18 (4476) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-15 01:34:18 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-15 01:34:18 (4493) [INFO] 
* 2024-02-15 01:34:18 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-15 01:34:18 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-15 01:34:18 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-15 01:34:19 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-15 01:34:19 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-15 01:34:19 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-15 01:34:19 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-15 01:34:19 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-15 01:34:19 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-15 01:34:19 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-15 01:34:19 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-15 01:34:19 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-15 01:34:25 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-15 01:34:25 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-15 01:34:25 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-15 01:34:25 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-15 01:34:25 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lL9y8TKG9p/ea_profile.json
* 2024-02-15 01:34:33 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lL9y8TKG9p/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-15 01:34:33 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-16 01:33:44 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-16 01:33:44 (1912) [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-02-16 01:33:44 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-16 01:33:45 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-16 01:33:45 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-16 01:33:45 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-16 01:33:45 (4463) [INFO] 
* 2024-02-16 01:33:45 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-16 01:33:45 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 2594.
* 2024-02-16 01:33:45 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:45 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:45 (4476) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-16 01:33:45 (4476) [INFO]     Started: Fri Feb 16 01:33:42 2024 - 00:03 ago
* 2024-02-16 01:33:45 (4476) [INFO]     State  : Sleeping, pid: 2594
* 2024-02-16 01:33:47 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:47 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:47 (4476) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-16 01:33:47 (4476) [INFO]     Started: Fri Feb 16 01:33:42 2024 - 00:05 ago
* 2024-02-16 01:33:47 (4476) [INFO]     State  : Sleeping, pid: 2594
* 2024-02-16 01:33:49 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:49 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:49 (4476) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-16 01:33:49 (4476) [INFO]     Started: Fri Feb 16 01:33:42 2024 - 00:07 ago
* 2024-02-16 01:33:49 (4476) [INFO]     State  : Sleeping, pid: 2594
* 2024-02-16 01:33:51 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:51 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:51 (4476) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-16 01:33:51 (4476) [INFO]     Started: Fri Feb 16 01:33:42 2024 - 00:09 ago
* 2024-02-16 01:33:51 (4476) [INFO]     State  : Sleeping, pid: 2594
* 2024-02-16 01:33:53 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 3009.
* 2024-02-16 01:33:53 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:53 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:53 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-16 01:33:53 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:02 ago
* 2024-02-16 01:33:53 (4476) [INFO]     State  : Running, pid: 3009
* 2024-02-16 01:33:55 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:55 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:55 (4476) [INFO]     Memory :  38 M RSS (331 MB VSZ)
* 2024-02-16 01:33:55 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:04 ago
* 2024-02-16 01:33:55 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:33:57 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:57 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:57 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:33:57 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:06 ago
* 2024-02-16 01:33:57 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:33:59 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:33:59 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:33:59 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:33:59 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:08 ago
* 2024-02-16 01:33:59 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:01 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:01 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:01 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:01 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:10 ago
* 2024-02-16 01:34:01 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:03 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:03 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:03 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:03 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:12 ago
* 2024-02-16 01:34:03 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:05 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:05 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:05 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:05 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:14 ago
* 2024-02-16 01:34:05 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:07 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:07 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:07 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:07 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:16 ago
* 2024-02-16 01:34:07 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:09 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:09 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:09 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:09 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:18 ago
* 2024-02-16 01:34:09 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:11 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:11 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:11 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:11 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:20 ago
* 2024-02-16 01:34:11 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:13 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:13 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:13 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:13 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:22 ago
* 2024-02-16 01:34:13 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:15 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:15 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:15 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:15 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:24 ago
* 2024-02-16 01:34:15 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:17 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:17 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:17 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:17 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:26 ago
* 2024-02-16 01:34:17 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:19 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:19 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:19 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:19 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:28 ago
* 2024-02-16 01:34:19 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:21 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:21 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:21 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:21 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:30 ago
* 2024-02-16 01:34:21 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:23 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:23 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:23 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:23 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:32 ago
* 2024-02-16 01:34:23 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:25 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:25 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:25 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:25 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:34 ago
* 2024-02-16 01:34:25 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:27 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:27 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:27 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:27 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:36 ago
* 2024-02-16 01:34:27 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:29 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:29 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:29 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:29 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:38 ago
* 2024-02-16 01:34:29 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:31 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:31 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:31 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:31 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:40 ago
* 2024-02-16 01:34:31 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:33 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:33 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:33 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:33 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:42 ago
* 2024-02-16 01:34:33 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:35 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:35 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:35 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:35 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:44 ago
* 2024-02-16 01:34:35 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:37 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:37 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:37 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:37 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:46 ago
* 2024-02-16 01:34:37 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:39 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:39 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:39 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:39 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:48 ago
* 2024-02-16 01:34:39 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:41 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:41 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:41 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:41 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:50 ago
* 2024-02-16 01:34:41 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:43 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:43 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:43 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:43 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:52 ago
* 2024-02-16 01:34:43 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:45 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:45 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:45 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:45 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:54 ago
* 2024-02-16 01:34:45 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:47 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:47 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:47 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:47 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:56 ago
* 2024-02-16 01:34:47 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:49 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:49 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:49 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:49 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 00:58 ago
* 2024-02-16 01:34:49 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:51 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:51 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:51 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:51 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:00 ago
* 2024-02-16 01:34:51 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:53 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:53 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:53 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:53 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:02 ago
* 2024-02-16 01:34:53 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:55 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:55 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:55 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:55 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:04 ago
* 2024-02-16 01:34:55 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:57 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:57 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:57 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:57 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:06 ago
* 2024-02-16 01:34:57 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:34:59 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:34:59 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:34:59 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:34:59 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:08 ago
* 2024-02-16 01:34:59 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:01 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:01 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:01 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:01 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:10 ago
* 2024-02-16 01:35:01 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:03 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:03 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:03 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:03 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:12 ago
* 2024-02-16 01:35:03 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:05 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:05 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:05 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:05 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:14 ago
* 2024-02-16 01:35:05 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:07 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:07 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:07 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:07 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:16 ago
* 2024-02-16 01:35:07 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:09 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:09 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:09 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:09 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:18 ago
* 2024-02-16 01:35:09 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:11 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:11 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:11 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:11 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:20 ago
* 2024-02-16 01:35:11 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:13 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:13 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:13 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:13 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:22 ago
* 2024-02-16 01:35:13 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:15 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:15 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:15 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:15 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:24 ago
* 2024-02-16 01:35:15 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:17 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:17 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:17 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:17 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:26 ago
* 2024-02-16 01:35:17 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:19 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:19 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:19 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:19 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:28 ago
* 2024-02-16 01:35:19 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:21 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:21 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:21 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:21 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:30 ago
* 2024-02-16 01:35:21 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:23 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:23 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:23 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:23 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:32 ago
* 2024-02-16 01:35:23 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:25 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-16 01:35:25 (4476) [INFO]   The other application is: yum
* 2024-02-16 01:35:25 (4476) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-16 01:35:25 (4476) [INFO]     Started: Fri Feb 16 01:33:51 2024 - 01:34 ago
* 2024-02-16 01:35:25 (4476) [INFO]     State  : Sleeping, pid: 3009
* 2024-02-16 01:35:27 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-16 01:35:27 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-16 01:35:27 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-16 01:35:27 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-16 01:35:27 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-16 01:35:27 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-16 01:35:27 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-16 01:35:27 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-16 01:35:27 (4476) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-16 01:35:27 (4493) [INFO] 
* 2024-02-16 01:35:27 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-16 01:35:27 (4463) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-16 01:35:34 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-16 01:35:34 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-16 01:35:34 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-16 01:35:34 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-16 01:35:34 (4476) [INFO] Trying other mirror.
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-16 01:35:34 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-16 01:35:34 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-16 01:35:34 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-16 01:35:34 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-16 01:35:34 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-16 01:35:34 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-16 01:35:34 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-16 01:35:34 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-16 01:35:34 (4476) [INFO]         or
* 2024-02-16 01:35:34 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-16 01:35:34 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-16 01:35:34 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-16 01:35:34 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-16 01:35:34 (4476) [INFO]         compromise:
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-16 01:35:34 (4476) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-16 01:35:34 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-16 01:35:34 (4493) [INFO] 
* 2024-02-16 01:35:34 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-16 01:35:34 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-16 01:35:34 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-16 01:35:35 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-16 01:35:35 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-16 01:35:35 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-16 01:35:35 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-16 01:35:35 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-16 01:35:35 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-16 01:35:35 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-16 01:35:35 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-16 01:35:35 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-16 01:35:40 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-16 01:35:40 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-16 01:35:40 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-16 01:35:40 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-16 01:35:40 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rz0YjddZuN/ea_profile.json
* 2024-02-16 01:35:44 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rz0YjddZuN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-16 01:35:44 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-17 01:34:56 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-17 01:34:56 (1912) [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-02-17 01:34:57 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-17 01:34:58 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-17 01:34:58 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-17 01:34:58 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-17 01:34:58 (4463) [INFO] 
* 2024-02-17 01:34:58 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-17 01:34:58 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 298094.
* 2024-02-17 01:34:58 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-17 01:34:58 (4476) [INFO]   The other application is: yum
* 2024-02-17 01:34:58 (4476) [INFO]     Memory :  36 M RSS (2.8 GB VSZ)
* 2024-02-17 01:34:58 (4476) [INFO]     Started: Sat Feb 17 01:34:53 2024 - 00:05 ago
* 2024-02-17 01:34:58 (4476) [INFO]     State  : Sleeping, pid: 298094
* 2024-02-17 01:35:00 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-17 01:35:00 (4476) [INFO]   The other application is: yum
* 2024-02-17 01:35:00 (4476) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-17 01:35:00 (4476) [INFO]     Started: Sat Feb 17 01:34:53 2024 - 00:07 ago
* 2024-02-17 01:35:00 (4476) [INFO]     State  : Sleeping, pid: 298094
* 2024-02-17 01:35:02 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-17 01:35:02 (4476) [INFO]   The other application is: yum
* 2024-02-17 01:35:02 (4476) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-17 01:35:02 (4476) [INFO]     Started: Sat Feb 17 01:34:53 2024 - 00:09 ago
* 2024-02-17 01:35:02 (4476) [INFO]     State  : Sleeping, pid: 298094
* 2024-02-17 01:35:04 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 298727.
* 2024-02-17 01:35:04 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-17 01:35:04 (4476) [INFO]   The other application is: yum
* 2024-02-17 01:35:04 (4476) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-17 01:35:04 (4476) [INFO]     Started: Sat Feb 17 01:35:02 2024 - 00:02 ago
* 2024-02-17 01:35:04 (4476) [INFO]     State  : Sleeping, pid: 298727
* 2024-02-17 01:35:06 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-17 01:35:06 (4476) [INFO]   The other application is: yum
* 2024-02-17 01:35:06 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-17 01:35:06 (4476) [INFO]     Started: Sat Feb 17 01:35:02 2024 - 00:04 ago
* 2024-02-17 01:35:06 (4476) [INFO]     State  : Sleeping, pid: 298727
* 2024-02-17 01:35:08 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-17 01:35:08 (4476) [INFO]   The other application is: yum
* 2024-02-17 01:35:08 (4476) [INFO]     Memory :  38 M RSS (548 MB VSZ)
* 2024-02-17 01:35:08 (4476) [INFO]     Started: Sat Feb 17 01:35:02 2024 - 00:06 ago
* 2024-02-17 01:35:08 (4476) [INFO]     State  : Sleeping, pid: 298727
* 2024-02-17 01:35:10 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-17 01:35:10 (4476) [INFO]   The other application is: yum
* 2024-02-17 01:35:10 (4476) [INFO]     Memory :  39 M RSS (549 MB VSZ)
* 2024-02-17 01:35:10 (4476) [INFO]     Started: Sat Feb 17 01:35:02 2024 - 00:08 ago
* 2024-02-17 01:35:10 (4476) [INFO]     State  : Sleeping, pid: 298727
* 2024-02-17 01:35:12 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-17 01:35:12 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-17 01:35:12 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-17 01:35:12 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-17 01:35:12 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-17 01:35:12 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-17 01:35:12 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-17 01:35:12 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-17 01:35:12 (4476) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-17 01:35:12 (4493) [INFO] 
* 2024-02-17 01:35:12 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-17 01:35:12 (4463) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-17 01:35:19 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-17 01:35:19 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-17 01:35:19 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-17 01:35:19 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-17 01:35:19 (4476) [INFO] Trying other mirror.
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-17 01:35:19 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-17 01:35:19 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-17 01:35:19 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-17 01:35:19 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-17 01:35:19 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-17 01:35:19 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-17 01:35:19 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-17 01:35:19 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-17 01:35:19 (4476) [INFO]         or
* 2024-02-17 01:35:19 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-17 01:35:19 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-17 01:35:19 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-17 01:35:19 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-17 01:35:19 (4476) [INFO]         compromise:
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-17 01:35:19 (4476) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-17 01:35:19 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-17 01:35:19 (4493) [INFO] 
* 2024-02-17 01:35:19 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-17 01:35:19 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-17 01:35:19 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-17 01:35:20 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-17 01:35:20 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-17 01:35:20 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-17 01:35:20 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-17 01:35:20 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-17 01:35:20 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-17 01:35:20 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-17 01:35:20 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-17 01:35:20 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-17 01:35:23 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-17 01:35:23 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-17 01:35:23 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-17 01:35:24 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-17 01:35:24 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lCTE7daGCt/ea_profile.json
* 2024-02-17 01:35:28 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lCTE7daGCt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-17 01:35:28 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-18 01:34:32 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-18 01:34:32 (1912) [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-02-18 01:34:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-18 01:34:33 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-18 01:34:33 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-18 01:34:33 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-18 01:34:33 (4463) [INFO] 
* 2024-02-18 01:34:33 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-18 01:34:34 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 578399.
* 2024-02-18 01:34:34 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-18 01:34:34 (4476) [INFO]   The other application is: yum
* 2024-02-18 01:34:34 (4476) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-18 01:34:34 (4476) [INFO]     Started: Sun Feb 18 01:34:29 2024 - 00:05 ago
* 2024-02-18 01:34:34 (4476) [INFO]     State  : Sleeping, pid: 578399
* 2024-02-18 01:34:36 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-18 01:34:36 (4476) [INFO]   The other application is: yum
* 2024-02-18 01:34:36 (4476) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-18 01:34:36 (4476) [INFO]     Started: Sun Feb 18 01:34:29 2024 - 00:07 ago
* 2024-02-18 01:34:36 (4476) [INFO]     State  : Sleeping, pid: 578399
* 2024-02-18 01:34:38 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-18 01:34:38 (4476) [INFO]   The other application is: yum
* 2024-02-18 01:34:38 (4476) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-18 01:34:38 (4476) [INFO]     Started: Sun Feb 18 01:34:29 2024 - 00:09 ago
* 2024-02-18 01:34:38 (4476) [INFO]     State  : Sleeping, pid: 578399
* 2024-02-18 01:34:40 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-18 01:34:40 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-18 01:34:40 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-18 01:34:40 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-18 01:34:40 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-18 01:34:40 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-18 01:34:40 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-18 01:34:40 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-18 01:34:40 (4476) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-18 01:34:40 (4493) [INFO] 
* 2024-02-18 01:34:40 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-18 01:34:40 (4463) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-18 01:34:50 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-18 01:34:50 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-18 01:34:50 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-18 01:34:50 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-18 01:34:50 (4476) [INFO] Trying other mirror.
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-18 01:34:50 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-18 01:34:50 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-18 01:34:50 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-18 01:34:50 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-18 01:34:50 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-18 01:34:50 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-18 01:34:50 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-18 01:34:50 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-18 01:34:50 (4476) [INFO]         or
* 2024-02-18 01:34:50 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-18 01:34:50 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-18 01:34:50 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-18 01:34:50 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-18 01:34:50 (4476) [INFO]         compromise:
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-18 01:34:50 (4476) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-18 01:34:50 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-18 01:34:50 (4493) [INFO] 
* 2024-02-18 01:34:50 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-18 01:34:50 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-18 01:34:50 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-18 01:34:51 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-18 01:34:51 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-18 01:34:51 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-18 01:34:51 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-18 01:34:51 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-18 01:34:51 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-18 01:34:51 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-18 01:34:51 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-18 01:34:51 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-18 01:34:54 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-18 01:34:54 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-18 01:34:54 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-18 01:34:54 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-18 01:34:54 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vCJytl6qse/ea_profile.json
* 2024-02-18 01:35:04 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vCJytl6qse/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-18 01:35:04 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-19 01:33:38 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-19 01:33:38 (1912) [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-02-19 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-19 01:33:39 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-19 01:33:39 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-19 01:33:39 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-19 01:33:39 (4463) [INFO] 
* 2024-02-19 01:33:39 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-19 01:33:39 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 843000.
* 2024-02-19 01:33:39 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-19 01:33:39 (4476) [INFO]   The other application is: yum
* 2024-02-19 01:33:39 (4476) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-19 01:33:39 (4476) [INFO]     Started: Mon Feb 19 01:33:34 2024 - 00:05 ago
* 2024-02-19 01:33:39 (4476) [INFO]     State  : Sleeping, pid: 843000
* 2024-02-19 01:33:41 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-19 01:33:41 (4476) [INFO]   The other application is: yum
* 2024-02-19 01:33:41 (4476) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-19 01:33:41 (4476) [INFO]     Started: Mon Feb 19 01:33:34 2024 - 00:07 ago
* 2024-02-19 01:33:41 (4476) [INFO]     State  : Sleeping, pid: 843000
* 2024-02-19 01:33:43 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-19 01:33:43 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-19 01:33:43 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-19 01:33:43 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-19 01:33:43 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-19 01:33:43 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-19 01:33:43 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-19 01:33:43 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-19 01:33:43 (4476) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-19 01:33:43 (4493) [INFO] 
* 2024-02-19 01:33:43 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-19 01:33:43 (4463) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-19 01:33:51 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-19 01:33:51 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-19 01:33:51 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-19 01:33:51 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-19 01:33:51 (4476) [INFO] Trying other mirror.
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-19 01:33:51 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-19 01:33:51 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-19 01:33:51 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-19 01:33:51 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-19 01:33:51 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-19 01:33:51 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-19 01:33:51 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-19 01:33:51 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-19 01:33:51 (4476) [INFO]         or
* 2024-02-19 01:33:51 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-19 01:33:51 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-19 01:33:51 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-19 01:33:51 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-19 01:33:51 (4476) [INFO]         compromise:
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-19 01:33:51 (4476) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-19 01:33:51 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-19 01:33:51 (4493) [INFO] 
* 2024-02-19 01:33:51 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-19 01:33:51 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-19 01:33:51 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-19 01:33:52 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-19 01:33:52 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-19 01:33:52 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-19 01:33:52 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-19 01:33:52 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-19 01:33:52 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-19 01:33:52 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-19 01:33:52 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-19 01:33:52 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-19 01:33:57 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-19 01:33:57 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-19 01:33:57 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-19 01:33:57 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-19 01:33:57 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cr5gAaOhBJ/ea_profile.json
* 2024-02-19 01:34:00 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cr5gAaOhBJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-19 01:34:00 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-20 01:34:18 (163) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-20 01:34:18 (1912) [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-02-20 01:34:18 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-20 01:34:19 (163) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-20 01:34:19 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-20 01:34:19 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-20 01:34:19 (4463) [INFO] 
* 2024-02-20 01:34:19 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-20 01:34:19 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 71808.
* 2024-02-20 01:34:19 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:19 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:19 (4476) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-20 01:34:19 (4476) [INFO]     Started: Tue Feb 20 01:34:15 2024 - 00:04 ago
* 2024-02-20 01:34:19 (4476) [INFO]     State  : Sleeping, pid: 71808
* 2024-02-20 01:34:21 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:21 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:21 (4476) [INFO]     Memory :  36 M RSS (2.8 GB VSZ)
* 2024-02-20 01:34:21 (4476) [INFO]     Started: Tue Feb 20 01:34:15 2024 - 00:06 ago
* 2024-02-20 01:34:21 (4476) [INFO]     State  : Sleeping, pid: 71808
* 2024-02-20 01:34:23 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:23 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:23 (4476) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-20 01:34:23 (4476) [INFO]     Started: Tue Feb 20 01:34:15 2024 - 00:08 ago
* 2024-02-20 01:34:23 (4476) [INFO]     State  : Sleeping, pid: 71808
* 2024-02-20 01:34:25 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:25 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:25 (4476) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-20 01:34:25 (4476) [INFO]     Started: Tue Feb 20 01:34:15 2024 - 00:10 ago
* 2024-02-20 01:34:25 (4476) [INFO]     State  : Sleeping, pid: 71808
* 2024-02-20 01:34:27 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:27 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:27 (4476) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-20 01:34:27 (4476) [INFO]     Started: Tue Feb 20 01:34:15 2024 - 00:12 ago
* 2024-02-20 01:34:27 (4476) [INFO]     State  : Sleeping, pid: 71808
* 2024-02-20 01:34:29 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 72225.
* 2024-02-20 01:34:29 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:29 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:29 (4476) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-20 01:34:29 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:01 ago
* 2024-02-20 01:34:29 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:31 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:31 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:31 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:31 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:03 ago
* 2024-02-20 01:34:31 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:33 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:33 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:33 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:33 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:05 ago
* 2024-02-20 01:34:33 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:35 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:35 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:35 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:35 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:07 ago
* 2024-02-20 01:34:35 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:37 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:37 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:37 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:37 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:09 ago
* 2024-02-20 01:34:37 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:39 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:39 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:39 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:39 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:11 ago
* 2024-02-20 01:34:39 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:41 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:41 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:41 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:41 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:13 ago
* 2024-02-20 01:34:41 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:43 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:43 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:43 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:43 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:15 ago
* 2024-02-20 01:34:43 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:45 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:45 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:45 (4476) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-20 01:34:45 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:17 ago
* 2024-02-20 01:34:45 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:47 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:47 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:47 (4476) [INFO]     Memory :  37 M RSS (1.3 GB VSZ)
* 2024-02-20 01:34:47 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:19 ago
* 2024-02-20 01:34:47 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:49 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-20 01:34:49 (4476) [INFO]   The other application is: yum
* 2024-02-20 01:34:49 (4476) [INFO]     Memory :  39 M RSS (1.3 GB VSZ)
* 2024-02-20 01:34:49 (4476) [INFO]     Started: Tue Feb 20 01:34:28 2024 - 00:21 ago
* 2024-02-20 01:34:49 (4476) [INFO]     State  : Sleeping, pid: 72225
* 2024-02-20 01:34:51 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-20 01:34:51 (4476) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-20 01:34:51 (4476) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-20 01:34:51 (4476) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-20 01:34:51 (4476) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-20 01:34:51 (4476) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-20 01:34:51 (4476) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-20 01:34:51 (4476) [INFO] Cleaning up list of fastest mirrors
* 2024-02-20 01:34:51 (4476) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-20 01:34:51 (4493) [INFO] 
* 2024-02-20 01:34:51 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-20 01:34:51 (4463) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-20 01:35:14 (4476) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-20 01:35:14 (4476) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-20 01:35:14 (4476) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-20 01:35:14 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-20 01:35:14 (4476) [INFO] Trying other mirror.
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-20 01:35:14 (4476) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-20 01:35:14 (4476) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-20 01:35:14 (4476) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-20 01:35:14 (4476) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-20 01:35:14 (4476) [INFO]         packages for the previous distribution release still work).
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-20 01:35:14 (4476) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-20 01:35:14 (4476) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-20 01:35:14 (4476) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-20 01:35:14 (4476) [INFO]         or
* 2024-02-20 01:35:14 (4476) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-20 01:35:14 (4476) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-20 01:35:14 (4476) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-20 01:35:14 (4476) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-20 01:35:14 (4476) [INFO]         compromise:
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-20 01:35:14 (4476) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-20 01:35:14 (4476) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-20 01:35:14 (4493) [INFO] 
* 2024-02-20 01:35:14 (4476) [INFO] Is this ok [y/N]: 
* 2024-02-20 01:35:14 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-20 01:35:14 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-20 01:35:15 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-20 01:35:15 (1781) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-20 01:35:15 (1781) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-20 01:35:15 (1764) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-20 01:35:15 (1764) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-20 01:35:15 (1781) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-20 01:35:15 (1781) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-20 01:35:15 (1764) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-20 01:35:15 (1781) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-20 01:35:33 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-20 01:35:33 (1705) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-20 01:35:33 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-20 01:35:34 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-20 01:35:34 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mIOOS7fhrV/ea_profile.json
* 2024-02-20 01:35:53 (310) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mIOOS7fhrV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-20 01:35:54 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-21 01:33:53 (170) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-21 01:33:53 (1849) [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-02-21 01:33:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-21 01:33:53 (170) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-21 01:33:54 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-21 01:33:54 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-21 01:33:54 (4911) [INFO] 
* 2024-02-21 01:33:54 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-21 01:33:54 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 353431.
* 2024-02-21 01:33:54 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:33:54 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:33:54 (4924) [INFO]     Memory :  36 M RSS (3.1 GB VSZ)
* 2024-02-21 01:33:54 (4924) [INFO]     Started: Wed Feb 21 01:33:50 2024 - 00:04 ago
* 2024-02-21 01:33:54 (4924) [INFO]     State  : Sleeping, pid: 353431
* 2024-02-21 01:33:56 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:33:56 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:33:56 (4924) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-21 01:33:56 (4924) [INFO]     Started: Wed Feb 21 01:33:50 2024 - 00:06 ago
* 2024-02-21 01:33:56 (4924) [INFO]     State  : Sleeping, pid: 353431
* 2024-02-21 01:33:58 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:33:58 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:33:58 (4924) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-21 01:33:58 (4924) [INFO]     Started: Wed Feb 21 01:33:50 2024 - 00:08 ago
* 2024-02-21 01:33:58 (4924) [INFO]     State  : Sleeping, pid: 353431
* 2024-02-21 01:34:00 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:34:00 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:34:00 (4924) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-21 01:34:00 (4924) [INFO]     Started: Wed Feb 21 01:33:50 2024 - 00:10 ago
* 2024-02-21 01:34:00 (4924) [INFO]     State  : Sleeping, pid: 353431
* 2024-02-21 01:34:02 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 353897.
* 2024-02-21 01:34:02 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:34:02 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:34:02 (4924) [INFO]     Memory :  37 M RSS (330 MB VSZ)
* 2024-02-21 01:34:02 (4924) [INFO]     Started: Wed Feb 21 01:34:00 2024 - 00:02 ago
* 2024-02-21 01:34:02 (4924) [INFO]     State  : Sleeping, pid: 353897
* 2024-02-21 01:34:04 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:34:04 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:34:04 (4924) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-21 01:34:04 (4924) [INFO]     Started: Wed Feb 21 01:34:00 2024 - 00:04 ago
* 2024-02-21 01:34:04 (4924) [INFO]     State  : Sleeping, pid: 353897
* 2024-02-21 01:34:06 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:34:06 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:34:06 (4924) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-21 01:34:06 (4924) [INFO]     Started: Wed Feb 21 01:34:00 2024 - 00:06 ago
* 2024-02-21 01:34:06 (4924) [INFO]     State  : Sleeping, pid: 353897
* 2024-02-21 01:34:08 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:34:08 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:34:08 (4924) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-21 01:34:08 (4924) [INFO]     Started: Wed Feb 21 01:34:00 2024 - 00:08 ago
* 2024-02-21 01:34:08 (4924) [INFO]     State  : Sleeping, pid: 353897
* 2024-02-21 01:34:10 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-21 01:34:10 (4924) [INFO]   The other application is: yum
* 2024-02-21 01:34:10 (4924) [INFO]     Memory :  39 M RSS (337 MB VSZ)
* 2024-02-21 01:34:10 (4924) [INFO]     Started: Wed Feb 21 01:34:00 2024 - 00:10 ago
* 2024-02-21 01:34:10 (4924) [INFO]     State  : Running, pid: 353897
* 2024-02-21 01:34:12 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-21 01:34:12 (4924) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-21 01:34:12 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-21 01:34:12 (4924) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-21 01:34:12 (4924) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-21 01:34:12 (4924) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-21 01:34:12 (4924) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-21 01:34:12 (4924) [INFO] Cleaning up list of fastest mirrors
* 2024-02-21 01:34:12 (4924) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-21 01:34:12 (4941) [INFO] 
* 2024-02-21 01:34:12 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-21 01:34:12 (4911) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-21 01:34:21 (4924) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-21 01:34:21 (4924) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-21 01:34:21 (4924) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-21 01:34:21 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-21 01:34:21 (4924) [INFO] Trying other mirror.
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-21 01:34:21 (4924) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-21 01:34:21 (4924) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-21 01:34:21 (4924) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-21 01:34:21 (4924) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-21 01:34:21 (4924) [INFO]         packages for the previous distribution release still work).
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-21 01:34:21 (4924) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-21 01:34:21 (4924) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-21 01:34:21 (4924) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-21 01:34:21 (4924) [INFO]         or
* 2024-02-21 01:34:21 (4924) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-21 01:34:21 (4924) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-21 01:34:21 (4924) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-21 01:34:21 (4924) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-21 01:34:21 (4924) [INFO]         compromise:
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-21 01:34:21 (4924) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-21 01:34:21 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-21 01:34:21 (4941) [INFO] 
* 2024-02-21 01:34:21 (4924) [INFO] Is this ok [y/N]: 
* 2024-02-21 01:34:21 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-21 01:34:21 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-21 01:34:22 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-21 01:34:22 (1718) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-21 01:34:22 (1718) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-21 01:34:22 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-21 01:34:22 (1701) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-21 01:34:22 (1718) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-21 01:34:22 (1718) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-21 01:34:22 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-21 01:34:22 (1718) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-21 01:34:26 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-21 01:34:26 (1642) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-21 01:34:26 (170) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-21 01:34:26 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-21 01:34:26 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/f0bJlwLLNr/ea_profile.json
* 2024-02-21 01:34:30 (317) [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/f0bJlwLLNr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-21 01:34:30 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-22 01:34:08 (170) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-22 01:34:08 (1849) [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-02-22 01:34:12 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-22 01:34:12 (170) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-22 01:34:12 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-22 01:34:12 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-22 01:34:12 (4911) [INFO] 
* 2024-02-22 01:34:13 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-22 01:34:13 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 627708.
* 2024-02-22 01:34:13 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-22 01:34:13 (4924) [INFO]   The other application is: yum
* 2024-02-22 01:34:13 (4924) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-22 01:34:13 (4924) [INFO]     Started: Thu Feb 22 01:34:06 2024 - 00:07 ago
* 2024-02-22 01:34:13 (4924) [INFO]     State  : Sleeping, pid: 627708
* 2024-02-22 01:34:15 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-22 01:34:15 (4924) [INFO]   The other application is: yum
* 2024-02-22 01:34:15 (4924) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-22 01:34:15 (4924) [INFO]     Started: Thu Feb 22 01:34:06 2024 - 00:09 ago
* 2024-02-22 01:34:15 (4924) [INFO]     State  : Sleeping, pid: 627708
* 2024-02-22 01:34:17 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 628062.
* 2024-02-22 01:34:17 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-22 01:34:17 (4924) [INFO]   The other application is: yum
* 2024-02-22 01:34:17 (4924) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-22 01:34:17 (4924) [INFO]     Started: Thu Feb 22 01:34:15 2024 - 00:02 ago
* 2024-02-22 01:34:17 (4924) [INFO]     State  : Sleeping, pid: 628062
* 2024-02-22 01:34:19 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-22 01:34:19 (4924) [INFO]   The other application is: yum
* 2024-02-22 01:34:19 (4924) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-22 01:34:19 (4924) [INFO]     Started: Thu Feb 22 01:34:15 2024 - 00:04 ago
* 2024-02-22 01:34:19 (4924) [INFO]     State  : Sleeping, pid: 628062
* 2024-02-22 01:34:21 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-22 01:34:21 (4924) [INFO]   The other application is: yum
* 2024-02-22 01:34:21 (4924) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-22 01:34:21 (4924) [INFO]     Started: Thu Feb 22 01:34:15 2024 - 00:06 ago
* 2024-02-22 01:34:21 (4924) [INFO]     State  : Sleeping, pid: 628062
* 2024-02-22 01:34:23 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-22 01:34:23 (4924) [INFO]   The other application is: yum
* 2024-02-22 01:34:23 (4924) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-22 01:34:23 (4924) [INFO]     Started: Thu Feb 22 01:34:15 2024 - 00:08 ago
* 2024-02-22 01:34:23 (4924) [INFO]     State  : Sleeping, pid: 628062
* 2024-02-22 01:34:25 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-22 01:34:25 (4924) [INFO]   The other application is: yum
* 2024-02-22 01:34:25 (4924) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-22 01:34:25 (4924) [INFO]     Started: Thu Feb 22 01:34:15 2024 - 00:10 ago
* 2024-02-22 01:34:25 (4924) [INFO]     State  : Sleeping, pid: 628062
* 2024-02-22 01:34:27 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-22 01:34:27 (4924) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-22 01:34:27 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-22 01:34:27 (4924) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-22 01:34:27 (4924) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-22 01:34:27 (4924) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-22 01:34:27 (4924) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-22 01:34:27 (4924) [INFO] Cleaning up list of fastest mirrors
* 2024-02-22 01:34:27 (4924) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-22 01:34:27 (4941) [INFO] 
* 2024-02-22 01:34:27 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-22 01:34:27 (4911) [INFO] 
* 2024-02-22 01:34:38 (4924) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-22 01:34:38 (4924) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-22 01:34:38 (4924) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-22 01:34:38 (4924) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-22 01:34:38 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-22 01:34:38 (4924) [INFO] Trying other mirror.
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-22 01:34:39 (4924) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-22 01:34:39 (4924) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-22 01:34:39 (4924) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-22 01:34:39 (4924) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-22 01:34:39 (4924) [INFO]         packages for the previous distribution release still work).
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-22 01:34:39 (4924) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-22 01:34:39 (4924) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-22 01:34:39 (4924) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-22 01:34:39 (4924) [INFO]         or
* 2024-02-22 01:34:39 (4924) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-22 01:34:39 (4924) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-22 01:34:39 (4924) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-22 01:34:39 (4924) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-22 01:34:39 (4924) [INFO]         compromise:
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-22 01:34:39 (4924) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-22 01:34:39 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-22 01:34:39 (4941) [INFO] 
* 2024-02-22 01:34:39 (4924) [INFO] Is this ok [y/N]: 
* 2024-02-22 01:34:39 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-22 01:34:39 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-22 01:34:40 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-22 01:34:40 (1718) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-22 01:34:40 (1718) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-22 01:34:40 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-22 01:34:40 (1701) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-22 01:34:40 (1718) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-22 01:34:40 (1718) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-22 01:34:40 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-22 01:34:40 (1718) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-22 01:34:47 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-22 01:34:47 (1642) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-22 01:34:47 (170) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-22 01:34:47 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-22 01:34:48 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JDtRlaEML0/ea_profile.json
* 2024-02-22 01:34:55 (317) [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/JDtRlaEML0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-22 01:34:55 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-23 01:33:33 (170) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-23 01:33:33 (1849) [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-02-23 01:33:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-23 01:33:34 (170) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-23 01:33:34 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-23 01:33:34 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-23 01:33:34 (4911) [INFO] 
* 2024-02-23 01:33:34 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-23 01:33:34 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 936823.
* 2024-02-23 01:33:34 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:34 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:34 (4924) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-23 01:33:34 (4924) [INFO]     Started: Fri Feb 23 01:33:29 2024 - 00:05 ago
* 2024-02-23 01:33:34 (4924) [INFO]     State  : Sleeping, pid: 936823
* 2024-02-23 01:33:36 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:36 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:36 (4924) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-23 01:33:36 (4924) [INFO]     Started: Fri Feb 23 01:33:29 2024 - 00:07 ago
* 2024-02-23 01:33:36 (4924) [INFO]     State  : Sleeping, pid: 936823
* 2024-02-23 01:33:38 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:38 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:38 (4924) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-23 01:33:38 (4924) [INFO]     Started: Fri Feb 23 01:33:29 2024 - 00:09 ago
* 2024-02-23 01:33:38 (4924) [INFO]     State  : Sleeping, pid: 936823
* 2024-02-23 01:33:41 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-23 01:33:41 (4924) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-23 01:33:41 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-23 01:33:41 (4924) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-23 01:33:41 (4924) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-23 01:33:41 (4924) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-23 01:33:41 (4924) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-23 01:33:41 (4924) [INFO] Cleaning up list of fastest mirrors
* 2024-02-23 01:33:41 (4924) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-23 01:33:41 (4941) [INFO] 
* 2024-02-23 01:33:41 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-23 01:33:41 (4911) [INFO] 
* 2024-02-23 01:33:41 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 937212.
* 2024-02-23 01:33:41 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:41 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:41 (4924) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-23 01:33:41 (4924) [INFO]     Started: Fri Feb 23 01:33:39 2024 - 00:02 ago
* 2024-02-23 01:33:41 (4924) [INFO]     State  : Sleeping, pid: 937212
* 2024-02-23 01:33:43 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:43 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:43 (4924) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-23 01:33:43 (4924) [INFO]     Started: Fri Feb 23 01:33:39 2024 - 00:04 ago
* 2024-02-23 01:33:43 (4924) [INFO]     State  : Sleeping, pid: 937212
* 2024-02-23 01:33:45 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:45 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:45 (4924) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-23 01:33:45 (4924) [INFO]     Started: Fri Feb 23 01:33:39 2024 - 00:06 ago
* 2024-02-23 01:33:45 (4924) [INFO]     State  : Sleeping, pid: 937212
* 2024-02-23 01:33:47 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:47 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:47 (4924) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-23 01:33:47 (4924) [INFO]     Started: Fri Feb 23 01:33:39 2024 - 00:08 ago
* 2024-02-23 01:33:47 (4924) [INFO]     State  : Sleeping, pid: 937212
* 2024-02-23 01:33:49 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-23 01:33:49 (4924) [INFO]   The other application is: yum
* 2024-02-23 01:33:49 (4924) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-23 01:33:49 (4924) [INFO]     Started: Fri Feb 23 01:33:39 2024 - 00:10 ago
* 2024-02-23 01:33:49 (4924) [INFO]     State  : Sleeping, pid: 937212
* 2024-02-23 01:33:53 (4924) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-23 01:33:53 (4924) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-23 01:33:53 (4924) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-23 01:33:53 (4924) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-23 01:33:53 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-23 01:33:53 (4924) [INFO] Trying other mirror.
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-23 01:33:53 (4924) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-23 01:33:53 (4924) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-23 01:33:53 (4924) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-23 01:33:53 (4924) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-23 01:33:53 (4924) [INFO]         packages for the previous distribution release still work).
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-23 01:33:53 (4924) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-23 01:33:53 (4924) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-23 01:33:53 (4924) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-23 01:33:53 (4924) [INFO]         or
* 2024-02-23 01:33:53 (4924) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-23 01:33:53 (4924) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-23 01:33:53 (4924) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-23 01:33:53 (4924) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-23 01:33:53 (4924) [INFO]         compromise:
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-23 01:33:53 (4924) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-23 01:33:53 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-23 01:33:53 (4941) [INFO] 
* 2024-02-23 01:33:53 (4924) [INFO] Is this ok [y/N]: 
* 2024-02-23 01:33:53 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-23 01:33:53 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-23 01:33:54 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-23 01:33:54 (1718) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-23 01:33:54 (1718) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-23 01:33:54 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-23 01:33:54 (1701) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-23 01:33:54 (1718) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-23 01:33:54 (1718) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-23 01:33:54 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-23 01:33:54 (1718) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-23 01:33:57 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-23 01:33:57 (1642) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-23 01:33:57 (170) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-23 01:33:57 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-23 01:33:57 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/J14dOreqzF/ea_profile.json
* 2024-02-23 01:34:01 (317) [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/J14dOreqzF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-23 01:34:01 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-24 01:34:36 (170) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-24 01:34:36 (1849) [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-02-24 01:34:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-24 01:34:37 (170) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-24 01:34:37 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-24 01:34:37 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-24 01:34:37 (4911) [INFO] 
* 2024-02-24 01:34:37 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-24 01:34:38 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 278058.
* 2024-02-24 01:34:38 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-24 01:34:38 (4924) [INFO]   The other application is: yum
* 2024-02-24 01:34:38 (4924) [INFO]     Memory :  36 M RSS (2.8 GB VSZ)
* 2024-02-24 01:34:38 (4924) [INFO]     Started: Sat Feb 24 01:34:33 2024 - 00:05 ago
* 2024-02-24 01:34:38 (4924) [INFO]     State  : Sleeping, pid: 278058
* 2024-02-24 01:34:40 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-24 01:34:40 (4924) [INFO]   The other application is: yum
* 2024-02-24 01:34:40 (4924) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-24 01:34:40 (4924) [INFO]     Started: Sat Feb 24 01:34:33 2024 - 00:07 ago
* 2024-02-24 01:34:40 (4924) [INFO]     State  : Sleeping, pid: 278058
* 2024-02-24 01:34:42 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-24 01:34:42 (4924) [INFO]   The other application is: yum
* 2024-02-24 01:34:42 (4924) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-24 01:34:42 (4924) [INFO]     Started: Sat Feb 24 01:34:33 2024 - 00:09 ago
* 2024-02-24 01:34:42 (4924) [INFO]     State  : Sleeping, pid: 278058
* 2024-02-24 01:34:44 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-24 01:34:44 (4924) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-24 01:34:44 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-24 01:34:44 (4924) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-24 01:34:44 (4924) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-24 01:34:44 (4924) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-24 01:34:44 (4924) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-24 01:34:44 (4924) [INFO] Cleaning up list of fastest mirrors
* 2024-02-24 01:34:44 (4924) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-24 01:34:44 (4941) [INFO] 
* 2024-02-24 01:34:44 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-24 01:34:44 (4911) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-24 01:34:50 (4924) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-24 01:34:50 (4924) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-24 01:34:50 (4924) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-24 01:34:50 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-24 01:34:50 (4924) [INFO] Trying other mirror.
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-24 01:34:50 (4924) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-24 01:34:50 (4924) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-24 01:34:50 (4924) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-24 01:34:50 (4924) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-24 01:34:50 (4924) [INFO]         packages for the previous distribution release still work).
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-24 01:34:50 (4924) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-24 01:34:50 (4924) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-24 01:34:50 (4924) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-24 01:34:50 (4924) [INFO]         or
* 2024-02-24 01:34:50 (4924) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-24 01:34:50 (4924) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-24 01:34:50 (4924) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-24 01:34:50 (4924) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-24 01:34:50 (4924) [INFO]         compromise:
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-24 01:34:50 (4924) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-24 01:34:50 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-24 01:34:50 (4941) [INFO] 
* 2024-02-24 01:34:50 (4924) [INFO] Is this ok [y/N]: 
* 2024-02-24 01:34:50 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-24 01:34:50 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-24 01:34:55 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-24 01:34:55 (1718) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-24 01:34:55 (1718) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-24 01:34:55 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-24 01:34:55 (1701) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-24 01:34:55 (1718) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-24 01:34:55 (1718) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-24 01:34:55 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-24 01:34:55 (1718) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-24 01:34:58 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-24 01:34:58 (1642) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-24 01:34:58 (170) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-24 01:34:58 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-24 01:34:58 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/41bCv6ABEe/ea_profile.json
* 2024-02-24 01:35:01 (317) [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/41bCv6ABEe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-24 01:35:01 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-25 01:34:55 (170) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-25 01:34:55 (1849) [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-02-25 01:34:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-25 01:34:57 (170) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-25 01:34:57 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-25 01:34:57 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-25 01:34:57 (4911) [INFO] 
* 2024-02-25 01:34:57 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-25 01:34:57 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 646472.
* 2024-02-25 01:34:57 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-25 01:34:57 (4924) [INFO]   The other application is: yum
* 2024-02-25 01:34:57 (4924) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-25 01:34:57 (4924) [INFO]     Started: Sun Feb 25 01:34:52 2024 - 00:05 ago
* 2024-02-25 01:34:57 (4924) [INFO]     State  : Sleeping, pid: 646472
* 2024-02-25 01:34:59 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 646790.
* 2024-02-25 01:34:59 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-25 01:34:59 (4924) [INFO]   The other application is: yum
* 2024-02-25 01:34:59 (4924) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-25 01:34:59 (4924) [INFO]     Started: Sun Feb 25 01:34:57 2024 - 00:02 ago
* 2024-02-25 01:34:59 (4924) [INFO]     State  : Sleeping, pid: 646790
* 2024-02-25 01:35:01 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-25 01:35:01 (4924) [INFO]   The other application is: yum
* 2024-02-25 01:35:01 (4924) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-02-25 01:35:01 (4924) [INFO]     Started: Sun Feb 25 01:34:57 2024 - 00:04 ago
* 2024-02-25 01:35:01 (4924) [INFO]     State  : Sleeping, pid: 646790
* 2024-02-25 01:35:03 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-25 01:35:03 (4924) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-25 01:35:03 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-25 01:35:03 (4924) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-25 01:35:03 (4924) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-25 01:35:03 (4924) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-25 01:35:03 (4924) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-25 01:35:03 (4924) [INFO] Cleaning up list of fastest mirrors
* 2024-02-25 01:35:03 (4924) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-25 01:35:03 (4941) [INFO] 
* 2024-02-25 01:35:03 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-25 01:35:03 (4911) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-25 01:35:11 (4924) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-25 01:35:11 (4924) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-25 01:35:11 (4924) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-25 01:35:11 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-25 01:35:11 (4924) [INFO] Trying other mirror.
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-25 01:35:11 (4924) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-25 01:35:11 (4924) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-25 01:35:11 (4924) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-25 01:35:11 (4924) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-25 01:35:11 (4924) [INFO]         packages for the previous distribution release still work).
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-25 01:35:11 (4924) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-25 01:35:11 (4924) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-25 01:35:11 (4924) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-25 01:35:11 (4924) [INFO]         or
* 2024-02-25 01:35:11 (4924) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-25 01:35:11 (4924) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-25 01:35:11 (4924) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-25 01:35:11 (4924) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-25 01:35:11 (4924) [INFO]         compromise:
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-25 01:35:11 (4924) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-25 01:35:11 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-25 01:35:11 (4941) [INFO] 
* 2024-02-25 01:35:11 (4924) [INFO] Is this ok [y/N]: 
* 2024-02-25 01:35:11 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-25 01:35:11 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-25 01:35:12 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-25 01:35:12 (1718) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-25 01:35:12 (1718) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-25 01:35:12 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-25 01:35:12 (1701) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-25 01:35:12 (1718) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-25 01:35:12 (1718) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-25 01:35:12 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-25 01:35:12 (1718) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-25 01:35:15 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-25 01:35:15 (1642) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-25 01:35:15 (170) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-25 01:35:15 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-25 01:35:15 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p9jJWDj4Mk/ea_profile.json
* 2024-02-25 01:35:18 (317) [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/p9jJWDj4Mk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-25 01:35:18 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-26 01:33:32 (170) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-26 01:33:32 (1849) [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-02-26 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-26 01:33:32 (170) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-26 01:33:33 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-26 01:33:33 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-26 01:33:33 (4911) [INFO] 
* 2024-02-26 01:33:33 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-26 01:33:33 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 1038472.
* 2024-02-26 01:33:33 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-26 01:33:33 (4924) [INFO]   The other application is: yum
* 2024-02-26 01:33:33 (4924) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-02-26 01:33:33 (4924) [INFO]     Started: Mon Feb 26 01:33:28 2024 - 00:05 ago
* 2024-02-26 01:33:33 (4924) [INFO]     State  : Sleeping, pid: 1038472
* 2024-02-26 01:33:35 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-26 01:33:35 (4924) [INFO]   The other application is: yum
* 2024-02-26 01:33:35 (4924) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-02-26 01:33:35 (4924) [INFO]     Started: Mon Feb 26 01:33:28 2024 - 00:07 ago
* 2024-02-26 01:33:35 (4924) [INFO]     State  : Sleeping, pid: 1038472
* 2024-02-26 01:33:37 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-26 01:33:37 (4924) [INFO]   The other application is: yum
* 2024-02-26 01:33:37 (4924) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-26 01:33:37 (4924) [INFO]     Started: Mon Feb 26 01:33:28 2024 - 00:09 ago
* 2024-02-26 01:33:37 (4924) [INFO]     State  : Sleeping, pid: 1038472
* 2024-02-26 01:33:39 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-26 01:33:39 (4924) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-26 01:33:39 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-26 01:33:39 (4924) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-26 01:33:39 (4924) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-26 01:33:39 (4924) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-26 01:33:39 (4924) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-26 01:33:39 (4924) [INFO] Cleaning up list of fastest mirrors
* 2024-02-26 01:33:39 (4924) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-26 01:33:39 (4941) [INFO] 
* 2024-02-26 01:33:39 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-26 01:33:39 (4911) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-26 01:33:46 (4924) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-26 01:33:46 (4924) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-26 01:33:46 (4924) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-26 01:33:46 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-26 01:33:46 (4924) [INFO] Trying other mirror.
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-26 01:33:46 (4924) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-26 01:33:46 (4924) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-26 01:33:46 (4924) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-26 01:33:46 (4924) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-26 01:33:46 (4924) [INFO]         packages for the previous distribution release still work).
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-26 01:33:46 (4924) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-26 01:33:46 (4924) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-26 01:33:46 (4924) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-26 01:33:46 (4924) [INFO]         or
* 2024-02-26 01:33:46 (4924) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-26 01:33:46 (4924) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-26 01:33:46 (4924) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-26 01:33:46 (4924) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-26 01:33:46 (4924) [INFO]         compromise:
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-26 01:33:46 (4924) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-26 01:33:46 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-26 01:33:46 (4941) [INFO] 
* 2024-02-26 01:33:46 (4924) [INFO] Is this ok [y/N]: 
* 2024-02-26 01:33:46 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-26 01:33:46 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-26 01:33:47 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-26 01:33:47 (1718) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-26 01:33:47 (1718) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-26 01:33:47 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-26 01:33:47 (1701) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-26 01:33:47 (1718) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-26 01:33:47 (1718) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-26 01:33:47 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-26 01:33:47 (1718) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-26 01:33:50 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-26 01:33:50 (1642) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-26 01:33:50 (170) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-26 01:33:50 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-26 01:33:50 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qW_ZPB_jOW/ea_profile.json
* 2024-02-26 01:33:53 (317) [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/qW_ZPB_jOW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-26 01:33:53 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-27 01:33:52 (170) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-27 01:33:52 (1849) [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-02-27 01:33:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-27 01:33:52 (170) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-27 01:33:53 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-27 01:33:53 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-27 01:33:53 (4911) [INFO] 
* 2024-02-27 01:33:53 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-27 01:33:53 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 27027.
* 2024-02-27 01:33:53 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-27 01:33:53 (4924) [INFO]   The other application is: yum
* 2024-02-27 01:33:53 (4924) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-27 01:33:53 (4924) [INFO]     Started: Tue Feb 27 01:33:47 2024 - 00:06 ago
* 2024-02-27 01:33:53 (4924) [INFO]     State  : Sleeping, pid: 27027
* 2024-02-27 01:33:55 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-27 01:33:55 (4924) [INFO]   The other application is: yum
* 2024-02-27 01:33:55 (4924) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-02-27 01:33:55 (4924) [INFO]     Started: Tue Feb 27 01:33:47 2024 - 00:08 ago
* 2024-02-27 01:33:55 (4924) [INFO]     State  : Sleeping, pid: 27027
* 2024-02-27 01:33:57 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-27 01:33:57 (4924) [INFO]   The other application is: yum
* 2024-02-27 01:33:57 (4924) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-02-27 01:33:57 (4924) [INFO]     Started: Tue Feb 27 01:33:47 2024 - 00:10 ago
* 2024-02-27 01:33:57 (4924) [INFO]     State  : Sleeping, pid: 27027
* 2024-02-27 01:33:59 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-27 01:33:59 (4924) [INFO]   The other application is: yum
* 2024-02-27 01:33:59 (4924) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-02-27 01:33:59 (4924) [INFO]     Started: Tue Feb 27 01:33:47 2024 - 00:12 ago
* 2024-02-27 01:33:59 (4924) [INFO]     State  : Sleeping, pid: 27027
* 2024-02-27 01:34:01 (4924) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 27530.
* 2024-02-27 01:34:01 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-27 01:34:01 (4924) [INFO]   The other application is: yum
* 2024-02-27 01:34:01 (4924) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-02-27 01:34:01 (4924) [INFO]     Started: Tue Feb 27 01:33:59 2024 - 00:02 ago
* 2024-02-27 01:34:01 (4924) [INFO]     State  : Sleeping, pid: 27530
* 2024-02-27 01:34:03 (4924) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-27 01:34:03 (4924) [INFO]   The other application is: yum
* 2024-02-27 01:34:03 (4924) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-02-27 01:34:03 (4924) [INFO]     Started: Tue Feb 27 01:33:59 2024 - 00:04 ago
* 2024-02-27 01:34:03 (4924) [INFO]     State  : Sleeping, pid: 27530
* 2024-02-27 01:34:05 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-27 01:34:05 (4924) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-27 01:34:05 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-27 01:34:05 (4924) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-27 01:34:05 (4924) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-27 01:34:05 (4924) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-27 01:34:05 (4924) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-27 01:34:05 (4924) [INFO] Cleaning up list of fastest mirrors
* 2024-02-27 01:34:05 (4924) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-27 01:34:05 (4941) [INFO] 
* 2024-02-27 01:34:05 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-27 01:34:05 (4911) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-27 01:34:15 (4924) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-27 01:34:15 (4924) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-27 01:34:15 (4924) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-27 01:34:15 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-27 01:34:15 (4924) [INFO] Trying other mirror.
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-27 01:34:15 (4924) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-27 01:34:15 (4924) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-27 01:34:15 (4924) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-27 01:34:15 (4924) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-27 01:34:15 (4924) [INFO]         packages for the previous distribution release still work).
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-27 01:34:15 (4924) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-27 01:34:15 (4924) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-27 01:34:15 (4924) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-27 01:34:15 (4924) [INFO]         or
* 2024-02-27 01:34:15 (4924) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-27 01:34:15 (4924) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-27 01:34:15 (4924) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-27 01:34:15 (4924) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-27 01:34:15 (4924) [INFO]         compromise:
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-27 01:34:15 (4924) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-27 01:34:15 (4924) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-27 01:34:15 (4941) [INFO] 
* 2024-02-27 01:34:15 (4924) [INFO] Is this ok [y/N]: 
* 2024-02-27 01:34:15 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-27 01:34:15 (170) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-27 01:34:17 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-27 01:34:17 (1718) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-27 01:34:17 (1718) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-27 01:34:17 (1701) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-27 01:34:17 (1701) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-27 01:34:17 (1718) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-27 01:34:17 (1718) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-27 01:34:17 (1701) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-27 01:34:17 (1718) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-27 01:34:20 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-27 01:34:20 (1642) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-27 01:34:20 (170) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-27 01:34:20 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-27 01:34:22 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ojwqw5u6CO/ea_profile.json
* 2024-02-27 01:34:25 (317) [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/ojwqw5u6CO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-27 01:34:25 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-28 01:33:37 (173) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-28 01:33:37 (1895) [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-02-28 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-28 01:33:38 (173) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-28 01:33:38 (1828) [INFO] Checking if your system is up to date: 
* 2024-02-28 01:33:38 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-02-28 01:33:38 (5105) [INFO] 
* 2024-02-28 01:33:38 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-28 01:33:38 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 256839.
* 2024-02-28 01:33:38 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-28 01:33:38 (5118) [INFO]   The other application is: yum
* 2024-02-28 01:33:38 (5118) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-02-28 01:33:38 (5118) [INFO]     Started: Wed Feb 28 01:33:33 2024 - 00:05 ago
* 2024-02-28 01:33:38 (5118) [INFO]     State  : Sleeping, pid: 256839
* 2024-02-28 01:33:40 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-28 01:33:40 (5118) [INFO]   The other application is: yum
* 2024-02-28 01:33:40 (5118) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-28 01:33:40 (5118) [INFO]     Started: Wed Feb 28 01:33:33 2024 - 00:07 ago
* 2024-02-28 01:33:40 (5118) [INFO]     State  : Sleeping, pid: 256839
* 2024-02-28 01:33:42 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-28 01:33:42 (5118) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-28 01:33:42 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-28 01:33:42 (5118) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-28 01:33:42 (5118) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-28 01:33:42 (5118) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-28 01:33:42 (5118) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-28 01:33:42 (5118) [INFO] Cleaning up list of fastest mirrors
* 2024-02-28 01:33:42 (5118) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-02-28 01:33:42 (5135) [INFO] 
* 2024-02-28 01:33:42 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-28 01:33:42 (5105) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-28 01:33:54 (5118) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-28 01:33:54 (5118) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-28 01:33:54 (5118) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-28 01:33:54 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-28 01:33:54 (5118) [INFO] Trying other mirror.
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-28 01:33:54 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-28 01:33:54 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-28 01:33:54 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-28 01:33:54 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-28 01:33:54 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-28 01:33:54 (5118) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-28 01:33:54 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-28 01:33:54 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-28 01:33:54 (5118) [INFO]         or
* 2024-02-28 01:33:54 (5118) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-28 01:33:54 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-28 01:33:54 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-28 01:33:54 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-28 01:33:54 (5118) [INFO]         compromise:
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-28 01:33:54 (5118) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-28 01:33:54 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-28 01:33:54 (5135) [INFO] 
* 2024-02-28 01:33:54 (5118) [INFO] Is this ok [y/N]: 
* 2024-02-28 01:33:54 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-28 01:33:54 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-28 01:33:55 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-28 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-28 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-28 01:33:55 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-28 01:33:55 (1747) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-28 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-28 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-28 01:33:55 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-28 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-28 01:34:00 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-28 01:34:00 (1688) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-28 01:34:00 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-28 01:34:00 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-28 01:34:00 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y4U07JLwSF/ea_profile.json
* 2024-02-28 01:34:17 (322) [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/y4U07JLwSF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-02-28 01:34:17 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-29 01:33:46 (173) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-02-29 01:33:46 (1895) [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-02-29 01:33:46 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-02-29 01:33:46 (173) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-02-29 01:33:47 (1828) [INFO] Checking if your system is up to date: 
* 2024-02-29 01:33:47 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-02-29 01:33:47 (5105) [INFO] 
* 2024-02-29 01:33:47 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-29 01:33:47 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 677793.
* 2024-02-29 01:33:47 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-29 01:33:47 (5118) [INFO]   The other application is: yum
* 2024-02-29 01:33:47 (5118) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-02-29 01:33:47 (5118) [INFO]     Started: Thu Feb 29 01:33:42 2024 - 00:05 ago
* 2024-02-29 01:33:47 (5118) [INFO]     State  : Sleeping, pid: 677793
* 2024-02-29 01:33:49 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-29 01:33:49 (5118) [INFO]   The other application is: yum
* 2024-02-29 01:33:49 (5118) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-02-29 01:33:49 (5118) [INFO]     Started: Thu Feb 29 01:33:42 2024 - 00:07 ago
* 2024-02-29 01:33:49 (5118) [INFO]     State  : Sleeping, pid: 677793
* 2024-02-29 01:33:51 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 678130.
* 2024-02-29 01:33:51 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-29 01:33:51 (5118) [INFO]   The other application is: yum
* 2024-02-29 01:33:51 (5118) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-02-29 01:33:51 (5118) [INFO]     Started: Thu Feb 29 01:33:49 2024 - 00:02 ago
* 2024-02-29 01:33:51 (5118) [INFO]     State  : Sleeping, pid: 678130
* 2024-02-29 01:33:53 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-29 01:33:53 (5118) [INFO]   The other application is: yum
* 2024-02-29 01:33:53 (5118) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-02-29 01:33:53 (5118) [INFO]     Started: Thu Feb 29 01:33:49 2024 - 00:04 ago
* 2024-02-29 01:33:53 (5118) [INFO]     State  : Sleeping, pid: 678130
* 2024-02-29 01:33:55 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-02-29 01:33:55 (5118) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-02-29 01:33:55 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-29 01:33:55 (5118) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-02-29 01:33:55 (5118) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-02-29 01:33:55 (5118) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-02-29 01:33:55 (5118) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-02-29 01:33:55 (5118) [INFO] Cleaning up list of fastest mirrors
* 2024-02-29 01:33:55 (5118) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-02-29 01:33:55 (5135) [INFO] 
* 2024-02-29 01:33:55 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-29 01:33:55 (5105) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO] Importing GPG key 0x98AB5139:
* 2024-02-29 01:34:04 (5118) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-02-29 01:34:04 (5118) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-02-29 01:34:04 (5118) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-02-29 01:34:04 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-29 01:34:04 (5118) [INFO] Trying other mirror.
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-02-29 01:34:04 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-29 01:34:04 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-29 01:34:04 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-29 01:34:04 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-29 01:34:04 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-29 01:34:04 (5118) [INFO]             yum --disablerepo=virtualbox ...
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-29 01:34:04 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-29 01:34:04 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]             yum-config-manager --disable virtualbox
* 2024-02-29 01:34:04 (5118) [INFO]         or
* 2024-02-29 01:34:04 (5118) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-29 01:34:04 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-29 01:34:04 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-29 01:34:04 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-29 01:34:04 (5118) [INFO]         compromise:
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-02-29 01:34:04 (5118) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-02-29 01:34:04 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-29 01:34:04 (5135) [INFO] 
* 2024-02-29 01:34:04 (5118) [INFO] Is this ok [y/N]: 
* 2024-02-29 01:34:04 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-29 01:34:04 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-29 01:34:06 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-02-29 01:34:06 (1764) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-02-29 01:34:06 (1764) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-02-29 01:34:06 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-29 01:34:06 (1747) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-02-29 01:34:06 (1764) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-02-29 01:34:06 (1764) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-02-29 01:34:06 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-02-29 01:34:06 (1764) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-02-29 01:34:12 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-29 01:34:12 (1688) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-02-29 01:34:12 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-29 01:34:12 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-29 01:34:12 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q1F6oH3_gU/ea_profile.json
* 2024-02-29 01:34:17 (322) [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/q1F6oH3_gU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-02-29 01:34:17 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-01 01:34:44 (173) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-01 01:34:44 (1895) [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-03-01 01:34:44 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-01 01:34:45 (173) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-01 01:34:45 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-01 01:34:45 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-01 01:34:45 (5105) [INFO] 
* 2024-03-01 01:34:45 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-01 01:34:46 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 22612.
* 2024-03-01 01:34:46 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-01 01:34:46 (5118) [INFO]   The other application is: yum
* 2024-03-01 01:34:46 (5118) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-03-01 01:34:46 (5118) [INFO]     Started: Fri Mar  1 01:34:39 2024 - 00:07 ago
* 2024-03-01 01:34:46 (5118) [INFO]     State  : Sleeping, pid: 22612
* 2024-03-01 01:34:48 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-01 01:34:48 (5118) [INFO]   The other application is: yum
* 2024-03-01 01:34:48 (5118) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-01 01:34:48 (5118) [INFO]     Started: Fri Mar  1 01:34:39 2024 - 00:09 ago
* 2024-03-01 01:34:48 (5118) [INFO]     State  : Sleeping, pid: 22612
* 2024-03-01 01:34:50 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-01 01:34:50 (5118) [INFO]   The other application is: yum
* 2024-03-01 01:34:50 (5118) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-01 01:34:50 (5118) [INFO]     Started: Fri Mar  1 01:34:39 2024 - 00:11 ago
* 2024-03-01 01:34:50 (5118) [INFO]     State  : Sleeping, pid: 22612
* 2024-03-01 01:34:52 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-01 01:34:52 (5118) [INFO]   The other application is: yum
* 2024-03-01 01:34:52 (5118) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-01 01:34:52 (5118) [INFO]     Started: Fri Mar  1 01:34:39 2024 - 00:13 ago
* 2024-03-01 01:34:52 (5118) [INFO]     State  : Sleeping, pid: 22612
* 2024-03-01 01:34:54 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 23121.
* 2024-03-01 01:34:54 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-01 01:34:54 (5118) [INFO]   The other application is: yum
* 2024-03-01 01:34:54 (5118) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-03-01 01:34:54 (5118) [INFO]     Started: Fri Mar  1 01:34:51 2024 - 00:03 ago
* 2024-03-01 01:34:54 (5118) [INFO]     State  : Sleeping, pid: 23121
* 2024-03-01 01:34:56 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-01 01:34:56 (5118) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-01 01:34:56 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-01 01:34:56 (5118) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-01 01:34:56 (5118) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-01 01:34:56 (5118) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-01 01:34:56 (5118) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-01 01:34:56 (5118) [INFO] Cleaning up list of fastest mirrors
* 2024-03-01 01:34:56 (5118) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-03-01 01:34:56 (5135) [INFO] 
* 2024-03-01 01:34:56 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-01 01:34:56 (5105) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-01 01:35:03 (5118) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-01 01:35:03 (5118) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-01 01:35:03 (5118) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-01 01:35:03 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-01 01:35:03 (5118) [INFO] Trying other mirror.
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-01 01:35:03 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-01 01:35:03 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-01 01:35:03 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-01 01:35:03 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-01 01:35:03 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-01 01:35:03 (5118) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-01 01:35:03 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-01 01:35:03 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-01 01:35:03 (5118) [INFO]         or
* 2024-03-01 01:35:03 (5118) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-01 01:35:03 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-01 01:35:03 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-01 01:35:03 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-01 01:35:03 (5118) [INFO]         compromise:
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-01 01:35:03 (5118) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-01 01:35:03 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-01 01:35:03 (5135) [INFO] 
* 2024-03-01 01:35:03 (5118) [INFO] Is this ok [y/N]: 
* 2024-03-01 01:35:03 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-01 01:35:03 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-03-01 01:35:04 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-01 01:35:04 (1764) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-01 01:35:04 (1764) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-01 01:35:04 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-01 01:35:04 (1747) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-01 01:35:04 (1764) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-01 01:35:04 (1764) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-01 01:35:04 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-01 01:35:04 (1764) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-01 01:35:09 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-01 01:35:09 (1688) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-01 01:35:09 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-01 01:35:09 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-01 01:35:09 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hkcraUHJTY/ea_profile.json
* 2024-03-01 01:35:14 (322) [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/hkcraUHJTY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-01 01:35:14 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-02 01:34:42 (173) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-02 01:34:42 (1895) [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-03-02 01:34:42 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-02 01:34:43 (173) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-02 01:34:43 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-02 01:34:43 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-02 01:34:43 (5105) [INFO] 
* 2024-03-02 01:34:43 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-02 01:34:43 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 419617.
* 2024-03-02 01:34:43 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-02 01:34:43 (5118) [INFO]   The other application is: yum
* 2024-03-02 01:34:43 (5118) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-03-02 01:34:43 (5118) [INFO]     Started: Sat Mar  2 01:34:39 2024 - 00:04 ago
* 2024-03-02 01:34:43 (5118) [INFO]     State  : Sleeping, pid: 419617
* 2024-03-02 01:34:45 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-02 01:34:45 (5118) [INFO]   The other application is: yum
* 2024-03-02 01:34:45 (5118) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-03-02 01:34:45 (5118) [INFO]     Started: Sat Mar  2 01:34:39 2024 - 00:06 ago
* 2024-03-02 01:34:45 (5118) [INFO]     State  : Sleeping, pid: 419617
* 2024-03-02 01:34:47 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-02 01:34:47 (5118) [INFO]   The other application is: yum
* 2024-03-02 01:34:47 (5118) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-02 01:34:47 (5118) [INFO]     Started: Sat Mar  2 01:34:39 2024 - 00:08 ago
* 2024-03-02 01:34:47 (5118) [INFO]     State  : Sleeping, pid: 419617
* 2024-03-02 01:34:49 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-02 01:34:49 (5118) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-02 01:34:49 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-02 01:34:49 (5118) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-02 01:34:49 (5118) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-02 01:34:49 (5118) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-02 01:34:49 (5118) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-02 01:34:49 (5118) [INFO] Cleaning up list of fastest mirrors
* 2024-03-02 01:34:49 (5118) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-03-02 01:34:49 (5135) [INFO] 
* 2024-03-02 01:34:49 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-02 01:34:49 (5105) [INFO] 
* 2024-03-02 01:34:50 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 419995.
* 2024-03-02 01:34:50 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-02 01:34:50 (5118) [INFO]   The other application is: yum
* 2024-03-02 01:34:50 (5118) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-03-02 01:34:50 (5118) [INFO]     Started: Sat Mar  2 01:34:48 2024 - 00:02 ago
* 2024-03-02 01:34:50 (5118) [INFO]     State  : Sleeping, pid: 419995
* 2024-03-02 01:34:52 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-02 01:34:52 (5118) [INFO]   The other application is: yum
* 2024-03-02 01:34:52 (5118) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-03-02 01:34:52 (5118) [INFO]     Started: Sat Mar  2 01:34:48 2024 - 00:04 ago
* 2024-03-02 01:34:52 (5118) [INFO]     State  : Sleeping, pid: 419995
* 2024-03-02 01:34:54 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-02 01:34:54 (5118) [INFO]   The other application is: yum
* 2024-03-02 01:34:54 (5118) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-03-02 01:34:54 (5118) [INFO]     Started: Sat Mar  2 01:34:48 2024 - 00:06 ago
* 2024-03-02 01:34:54 (5118) [INFO]     State  : Sleeping, pid: 419995
* 2024-03-02 01:34:56 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-02 01:34:56 (5118) [INFO]   The other application is: yum
* 2024-03-02 01:34:56 (5118) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-02 01:34:56 (5118) [INFO]     Started: Sat Mar  2 01:34:48 2024 - 00:08 ago
* 2024-03-02 01:34:56 (5118) [INFO]     State  : Sleeping, pid: 419995
* 2024-03-02 01:35:02 (5118) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-02 01:35:02 (5118) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-02 01:35:02 (5118) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-02 01:35:02 (5118) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-02 01:35:02 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-02 01:35:02 (5118) [INFO] Trying other mirror.
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-02 01:35:02 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-02 01:35:02 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-02 01:35:02 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-02 01:35:02 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-02 01:35:02 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-02 01:35:02 (5118) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-02 01:35:02 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-02 01:35:02 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-02 01:35:02 (5118) [INFO]         or
* 2024-03-02 01:35:02 (5118) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-02 01:35:02 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-02 01:35:02 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-02 01:35:02 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-02 01:35:02 (5118) [INFO]         compromise:
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-02 01:35:02 (5118) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-02 01:35:02 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-02 01:35:02 (5135) [INFO] 
* 2024-03-02 01:35:02 (5118) [INFO] Is this ok [y/N]: 
* 2024-03-02 01:35:02 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-02 01:35:02 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-03-02 01:35:03 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-02 01:35:03 (1764) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-02 01:35:03 (1764) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-02 01:35:03 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-02 01:35:03 (1747) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-02 01:35:03 (1764) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-02 01:35:03 (1764) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-02 01:35:03 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-02 01:35:03 (1764) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-02 01:35:11 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-02 01:35:11 (1688) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-02 01:35:11 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-02 01:35:11 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-02 01:35:11 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dQvrNGPfwH/ea_profile.json
* 2024-03-02 01:35:16 (322) [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/dQvrNGPfwH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-02 01:35:16 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-03 01:35:00 (173) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-03 01:35:00 (1895) [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-03-03 01:35:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-03 01:35:01 (173) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-03 01:35:01 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-03 01:35:01 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-03 01:35:01 (5105) [INFO] 
* 2024-03-03 01:35:01 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-03 01:35:02 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 757070.
* 2024-03-03 01:35:02 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-03 01:35:02 (5118) [INFO]   The other application is: yum
* 2024-03-03 01:35:02 (5118) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-03-03 01:35:02 (5118) [INFO]     Started: Sun Mar  3 01:34:57 2024 - 00:05 ago
* 2024-03-03 01:35:02 (5118) [INFO]     State  : Sleeping, pid: 757070
* 2024-03-03 01:35:04 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-03 01:35:04 (5118) [INFO]   The other application is: yum
* 2024-03-03 01:35:04 (5118) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-03-03 01:35:04 (5118) [INFO]     Started: Sun Mar  3 01:34:57 2024 - 00:07 ago
* 2024-03-03 01:35:04 (5118) [INFO]     State  : Sleeping, pid: 757070
* 2024-03-03 01:35:06 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-03 01:35:06 (5118) [INFO]   The other application is: yum
* 2024-03-03 01:35:06 (5118) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-03 01:35:06 (5118) [INFO]     Started: Sun Mar  3 01:34:57 2024 - 00:09 ago
* 2024-03-03 01:35:06 (5118) [INFO]     State  : Sleeping, pid: 757070
* 2024-03-03 01:35:08 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-03 01:35:08 (5118) [INFO]   The other application is: yum
* 2024-03-03 01:35:08 (5118) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-03 01:35:08 (5118) [INFO]     Started: Sun Mar  3 01:34:57 2024 - 00:11 ago
* 2024-03-03 01:35:08 (5118) [INFO]     State  : Sleeping, pid: 757070
* 2024-03-03 01:35:10 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-03 01:35:10 (5118) [INFO]   The other application is: yum
* 2024-03-03 01:35:10 (5118) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-03 01:35:10 (5118) [INFO]     Started: Sun Mar  3 01:34:57 2024 - 00:13 ago
* 2024-03-03 01:35:10 (5118) [INFO]     State  : Sleeping, pid: 757070
* 2024-03-03 01:35:12 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 758211.
* 2024-03-03 01:35:12 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-03 01:35:12 (5118) [INFO]   The other application is: yum
* 2024-03-03 01:35:12 (5118) [INFO]     Memory :  37 M RSS (330 MB VSZ)
* 2024-03-03 01:35:12 (5118) [INFO]     Started: Sun Mar  3 01:35:10 2024 - 00:02 ago
* 2024-03-03 01:35:12 (5118) [INFO]     State  : Sleeping, pid: 758211
* 2024-03-03 01:35:14 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-03 01:35:14 (5118) [INFO]   The other application is: yum
* 2024-03-03 01:35:14 (5118) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-03-03 01:35:14 (5118) [INFO]     Started: Sun Mar  3 01:35:10 2024 - 00:04 ago
* 2024-03-03 01:35:14 (5118) [INFO]     State  : Sleeping, pid: 758211
* 2024-03-03 01:35:16 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-03 01:35:16 (5118) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-03 01:35:16 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-03 01:35:16 (5118) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-03 01:35:16 (5118) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-03 01:35:16 (5118) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-03 01:35:16 (5118) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-03 01:35:16 (5118) [INFO] Cleaning up list of fastest mirrors
* 2024-03-03 01:35:16 (5118) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-03-03 01:35:16 (5135) [INFO] 
* 2024-03-03 01:35:16 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-03 01:35:16 (5105) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-03 01:35:24 (5118) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-03 01:35:24 (5118) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-03 01:35:24 (5118) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-03 01:35:24 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-03 01:35:24 (5118) [INFO] Trying other mirror.
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-03 01:35:24 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-03 01:35:24 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-03 01:35:24 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-03 01:35:24 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-03 01:35:24 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-03 01:35:24 (5118) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-03 01:35:24 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-03 01:35:24 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-03 01:35:24 (5118) [INFO]         or
* 2024-03-03 01:35:24 (5118) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-03 01:35:24 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-03 01:35:24 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-03 01:35:24 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-03 01:35:24 (5118) [INFO]         compromise:
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-03 01:35:24 (5118) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-03 01:35:24 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-03 01:35:24 (5135) [INFO] 
* 2024-03-03 01:35:24 (5118) [INFO] Is this ok [y/N]: 
* 2024-03-03 01:35:24 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-03 01:35:24 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-03-03 01:35:24 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-03 01:35:24 (1764) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-03 01:35:24 (1764) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-03 01:35:24 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-03 01:35:24 (1747) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-03 01:35:24 (1764) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-03 01:35:24 (1764) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-03 01:35:24 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-03 01:35:24 (1764) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-03 01:35:27 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-03 01:35:27 (1688) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-03 01:35:27 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-03 01:35:27 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-03 01:35:27 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SkfWpyJQQk/ea_profile.json
* 2024-03-03 01:35:31 (322) [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/SkfWpyJQQk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-03 01:35:31 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-04 01:33:34 (173) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-04 01:33:34 (1895) [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-03-04 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-04 01:33:35 (173) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-04 01:33:35 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-04 01:33:35 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-04 01:33:35 (5105) [INFO] 
* 2024-03-04 01:33:35 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-04 01:33:36 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 42687.
* 2024-03-04 01:33:36 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-04 01:33:36 (5118) [INFO]   The other application is: yum
* 2024-03-04 01:33:36 (5118) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-04 01:33:36 (5118) [INFO]     Started: Mon Mar  4 01:33:31 2024 - 00:05 ago
* 2024-03-04 01:33:36 (5118) [INFO]     State  : Sleeping, pid: 42687
* 2024-03-04 01:33:38 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-04 01:33:38 (5118) [INFO]   The other application is: yum
* 2024-03-04 01:33:38 (5118) [INFO]     Memory :  37 M RSS (2.8 GB VSZ)
* 2024-03-04 01:33:38 (5118) [INFO]     Started: Mon Mar  4 01:33:31 2024 - 00:07 ago
* 2024-03-04 01:33:38 (5118) [INFO]     State  : Sleeping, pid: 42687
* 2024-03-04 01:33:40 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-04 01:33:40 (5118) [INFO]   The other application is: yum
* 2024-03-04 01:33:40 (5118) [INFO]     Memory :  38 M RSS (2.8 GB VSZ)
* 2024-03-04 01:33:40 (5118) [INFO]     Started: Mon Mar  4 01:33:31 2024 - 00:09 ago
* 2024-03-04 01:33:40 (5118) [INFO]     State  : Sleeping, pid: 42687
* 2024-03-04 01:33:42 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-04 01:33:42 (5118) [INFO]   The other application is: yum
* 2024-03-04 01:33:42 (5118) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-04 01:33:42 (5118) [INFO]     Started: Mon Mar  4 01:33:31 2024 - 00:11 ago
* 2024-03-04 01:33:42 (5118) [INFO]     State  : Sleeping, pid: 42687
* 2024-03-04 01:33:44 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-04 01:33:44 (5118) [INFO]   The other application is: yum
* 2024-03-04 01:33:44 (5118) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-04 01:33:44 (5118) [INFO]     Started: Mon Mar  4 01:33:31 2024 - 00:13 ago
* 2024-03-04 01:33:44 (5118) [INFO]     State  : Sleeping, pid: 42687
* 2024-03-04 01:33:46 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-04 01:33:46 (5118) [INFO]   The other application is: yum
* 2024-03-04 01:33:46 (5118) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-04 01:33:46 (5118) [INFO]     Started: Mon Mar  4 01:33:31 2024 - 00:15 ago
* 2024-03-04 01:33:46 (5118) [INFO]     State  : Sleeping, pid: 42687
* 2024-03-04 01:33:48 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-04 01:33:48 (5118) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-04 01:33:48 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-04 01:33:48 (5118) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-04 01:33:48 (5118) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-04 01:33:48 (5118) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-04 01:33:48 (5118) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-04 01:33:48 (5118) [INFO] Cleaning up list of fastest mirrors
* 2024-03-04 01:33:48 (5118) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-03-04 01:33:48 (5135) [INFO] 
* 2024-03-04 01:33:48 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-04 01:33:48 (5105) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-04 01:33:54 (5118) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-04 01:33:54 (5118) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-04 01:33:54 (5118) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-04 01:33:54 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-04 01:33:54 (5118) [INFO] Trying other mirror.
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-04 01:33:54 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-04 01:33:54 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-04 01:33:54 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-04 01:33:54 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-04 01:33:54 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-04 01:33:54 (5118) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-04 01:33:54 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-04 01:33:54 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-04 01:33:54 (5118) [INFO]         or
* 2024-03-04 01:33:54 (5118) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-04 01:33:54 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-04 01:33:54 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-04 01:33:54 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-04 01:33:54 (5118) [INFO]         compromise:
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-04 01:33:54 (5118) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-04 01:33:54 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-04 01:33:54 (5135) [INFO] 
* 2024-03-04 01:33:54 (5118) [INFO] Is this ok [y/N]: 
* 2024-03-04 01:33:54 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-04 01:33:54 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-03-04 01:33:55 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-04 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-04 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-04 01:33:55 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-04 01:33:55 (1747) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-04 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-04 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-04 01:33:55 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-04 01:33:55 (1764) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-04 01:33:58 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-04 01:33:58 (1688) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-04 01:33:58 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-04 01:33:58 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-04 01:33:58 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IJdQXWlnMJ/ea_profile.json
* 2024-03-04 01:34:04 (322) [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/IJdQXWlnMJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-04 01:34:04 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-05 01:33:50 (173) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-05 01:33:50 (1895) [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-03-05 01:33:50 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-05 01:33:50 (173) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-05 01:33:50 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-05 01:33:50 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-05 01:33:50 (5105) [INFO] 
* 2024-03-05 01:33:51 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-05 01:33:51 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 356746.
* 2024-03-05 01:33:51 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-05 01:33:51 (5118) [INFO]   The other application is: yum
* 2024-03-05 01:33:51 (5118) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-03-05 01:33:51 (5118) [INFO]     Started: Tue Mar  5 01:33:46 2024 - 00:05 ago
* 2024-03-05 01:33:51 (5118) [INFO]     State  : Sleeping, pid: 356746
* 2024-03-05 01:33:53 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-05 01:33:53 (5118) [INFO]   The other application is: yum
* 2024-03-05 01:33:53 (5118) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-03-05 01:33:53 (5118) [INFO]     Started: Tue Mar  5 01:33:46 2024 - 00:07 ago
* 2024-03-05 01:33:53 (5118) [INFO]     State  : Sleeping, pid: 356746
* 2024-03-05 01:33:55 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-05 01:33:55 (5118) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-05 01:33:55 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-05 01:33:55 (5118) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-05 01:33:55 (5118) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-05 01:33:55 (5118) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-05 01:33:55 (5118) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-05 01:33:55 (5118) [INFO] Cleaning up list of fastest mirrors
* 2024-03-05 01:33:55 (5118) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-03-05 01:33:55 (5135) [INFO] 
* 2024-03-05 01:33:55 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-05 01:33:55 (5105) [INFO] 
* 2024-03-05 01:33:55 (5118) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 357070.
* 2024-03-05 01:33:55 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-05 01:33:55 (5118) [INFO]   The other application is: yum
* 2024-03-05 01:33:55 (5118) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-03-05 01:33:55 (5118) [INFO]     Started: Tue Mar  5 01:33:53 2024 - 00:02 ago
* 2024-03-05 01:33:55 (5118) [INFO]     State  : Sleeping, pid: 357070
* 2024-03-05 01:33:57 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-05 01:33:57 (5118) [INFO]   The other application is: yum
* 2024-03-05 01:33:57 (5118) [INFO]     Memory :  38 M RSS (2.9 GB VSZ)
* 2024-03-05 01:33:57 (5118) [INFO]     Started: Tue Mar  5 01:33:53 2024 - 00:04 ago
* 2024-03-05 01:33:57 (5118) [INFO]     State  : Sleeping, pid: 357070
* 2024-03-05 01:33:59 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-05 01:33:59 (5118) [INFO]   The other application is: yum
* 2024-03-05 01:33:59 (5118) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-05 01:33:59 (5118) [INFO]     Started: Tue Mar  5 01:33:53 2024 - 00:06 ago
* 2024-03-05 01:33:59 (5118) [INFO]     State  : Sleeping, pid: 357070
* 2024-03-05 01:34:01 (5118) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-05 01:34:01 (5118) [INFO]   The other application is: yum
* 2024-03-05 01:34:01 (5118) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-05 01:34:01 (5118) [INFO]     Started: Tue Mar  5 01:33:53 2024 - 00:08 ago
* 2024-03-05 01:34:01 (5118) [INFO]     State  : Sleeping, pid: 357070
* 2024-03-05 01:34:09 (5118) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-05 01:34:09 (5118) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-05 01:34:09 (5118) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-05 01:34:09 (5118) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-05 01:34:09 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-05 01:34:09 (5118) [INFO] Trying other mirror.
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-05 01:34:09 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-05 01:34:09 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-05 01:34:09 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-05 01:34:09 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-05 01:34:09 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-05 01:34:09 (5118) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-05 01:34:09 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-05 01:34:09 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-05 01:34:09 (5118) [INFO]         or
* 2024-03-05 01:34:09 (5118) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-05 01:34:09 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-05 01:34:09 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-05 01:34:09 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-05 01:34:09 (5118) [INFO]         compromise:
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-05 01:34:09 (5118) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-05 01:34:09 (5118) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-05 01:34:09 (5135) [INFO] 
* 2024-03-05 01:34:09 (5118) [INFO] Is this ok [y/N]: 
* 2024-03-05 01:34:09 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-05 01:34:09 (173) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-03-05 01:34:10 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-05 01:34:10 (1764) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-05 01:34:10 (1764) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-05 01:34:10 (1747) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-05 01:34:10 (1747) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-05 01:34:10 (1764) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-05 01:34:10 (1764) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-05 01:34:10 (1747) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-05 01:34:10 (1764) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-05 01:34:15 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-05 01:34:15 (1688) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-05 01:34:15 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-05 01:34:15 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-05 01:34:15 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nphLouIyNE/ea_profile.json
* 2024-03-05 01:34:19 (322) [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/nphLouIyNE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-05 01:34:19 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-06 01:33:35 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-06 01:33:35 (1986) [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-03-06 01:33:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-06 01:33:36 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-06 01:33:36 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-06 01:33:36 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-06 01:33:36 (5196) [INFO] 
* 2024-03-06 01:33:36 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-06 01:33:36 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 638527.
* 2024-03-06 01:33:36 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-06 01:33:36 (5209) [INFO]   The other application is: yum
* 2024-03-06 01:33:36 (5209) [INFO]     Memory :  36 M RSS (2.8 GB VSZ)
* 2024-03-06 01:33:36 (5209) [INFO]     Started: Wed Mar  6 01:33:31 2024 - 00:05 ago
* 2024-03-06 01:33:36 (5209) [INFO]     State  : Sleeping, pid: 638527
* 2024-03-06 01:33:38 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-06 01:33:38 (5209) [INFO]   The other application is: yum
* 2024-03-06 01:33:38 (5209) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-03-06 01:33:38 (5209) [INFO]     Started: Wed Mar  6 01:33:31 2024 - 00:07 ago
* 2024-03-06 01:33:38 (5209) [INFO]     State  : Sleeping, pid: 638527
* 2024-03-06 01:33:40 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-06 01:33:40 (5209) [INFO]   The other application is: yum
* 2024-03-06 01:33:40 (5209) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-03-06 01:33:40 (5209) [INFO]     Started: Wed Mar  6 01:33:31 2024 - 00:09 ago
* 2024-03-06 01:33:40 (5209) [INFO]     State  : Sleeping, pid: 638527
* 2024-03-06 01:33:42 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-06 01:33:42 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-06 01:33:42 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-06 01:33:42 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-06 01:33:42 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-06 01:33:42 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-06 01:33:42 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-06 01:33:42 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-06 01:33:42 (5209) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-03-06 01:33:42 (5226) [INFO] 
* 2024-03-06 01:33:42 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-06 01:33:42 (5196) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-06 01:33:49 (5209) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-06 01:33:49 (5209) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-06 01:33:49 (5209) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-06 01:33:49 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-06 01:33:49 (5209) [INFO] Trying other mirror.
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-06 01:33:49 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-06 01:33:49 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-06 01:33:49 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-06 01:33:49 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-06 01:33:49 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-06 01:33:49 (5209) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-06 01:33:49 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-06 01:33:49 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-06 01:33:49 (5209) [INFO]         or
* 2024-03-06 01:33:49 (5209) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-06 01:33:49 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-06 01:33:49 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-06 01:33:49 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-06 01:33:49 (5209) [INFO]         compromise:
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-06 01:33:49 (5209) [INFO] 
* 2024-03-06 01:33:49 (5209) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-06 01:33:49 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-06 01:33:49 (5209) [INFO] Is this ok
* 2024-03-06 01:33:49 (5209) [INFO] [y/N]:
* 2024-03-06 01:33:49 (5226) [INFO] 
* 2024-03-06 01:33:49 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-06 01:33:54 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-06 01:33:54 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-06 01:33:54 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-06 01:33:54 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-06 01:33:54 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-06 01:33:54 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-06 01:33:54 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-06 01:33:54 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-06 01:33:54 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-06 01:33:58 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-06 01:33:58 (1701) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-06 01:33:58 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-06 01:33:58 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sjgQaj9Os6/ea_profile.json
* 2024-03-06 01:34:02 (339) [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/sjgQaj9Os6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-06 01:34:02 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-07 01:33:36 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-07 01:33:37 (1986) [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-03-07 01:33:37 (190) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-03-07 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-07 01:33:38 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-07 01:33:38 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-07 01:33:38 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-07 01:33:38 (5196) [INFO] 
* 2024-03-07 01:33:38 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-07 01:33:39 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 938293.
* 2024-03-07 01:33:39 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-07 01:33:39 (5209) [INFO]   The other application is: yum
* 2024-03-07 01:33:39 (5209) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-03-07 01:33:39 (5209) [INFO]     Started: Thu Mar  7 01:33:33 2024 - 00:06 ago
* 2024-03-07 01:33:39 (5209) [INFO]     State  : Sleeping, pid: 938293
* 2024-03-07 01:33:41 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 938629.
* 2024-03-07 01:33:41 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-07 01:33:41 (5209) [INFO]   The other application is: yum
* 2024-03-07 01:33:41 (5209) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-03-07 01:33:41 (5209) [INFO]     Started: Thu Mar  7 01:33:39 2024 - 00:02 ago
* 2024-03-07 01:33:41 (5209) [INFO]     State  : Sleeping, pid: 938629
* 2024-03-07 01:33:43 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-07 01:33:43 (5209) [INFO]   The other application is: yum
* 2024-03-07 01:33:43 (5209) [INFO]     Memory :  37 M RSS (763 MB VSZ)
* 2024-03-07 01:33:43 (5209) [INFO]     Started: Thu Mar  7 01:33:39 2024 - 00:04 ago
* 2024-03-07 01:33:43 (5209) [INFO]     State  : Sleeping, pid: 938629
* 2024-03-07 01:33:45 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-07 01:33:45 (5209) [INFO]   The other application is: yum
* 2024-03-07 01:33:45 (5209) [INFO]     Memory :  38 M RSS (740 MB VSZ)
* 2024-03-07 01:33:45 (5209) [INFO]     Started: Thu Mar  7 01:33:39 2024 - 00:06 ago
* 2024-03-07 01:33:45 (5209) [INFO]     State  : Sleeping, pid: 938629
* 2024-03-07 01:33:47 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-07 01:33:47 (5209) [INFO]   The other application is: yum
* 2024-03-07 01:33:47 (5209) [INFO]     Memory :  39 M RSS (741 MB VSZ)
* 2024-03-07 01:33:47 (5209) [INFO]     Started: Thu Mar  7 01:33:39 2024 - 00:08 ago
* 2024-03-07 01:33:47 (5209) [INFO]     State  : Sleeping, pid: 938629
* 2024-03-07 01:33:49 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-07 01:33:49 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-07 01:33:49 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-07 01:33:49 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-07 01:33:49 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-07 01:33:49 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-07 01:33:49 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-07 01:33:49 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-07 01:33:49 (5209) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-03-07 01:33:49 (5226) [INFO] 
* 2024-03-07 01:33:49 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-07 01:33:49 (5196) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-07 01:33:56 (5209) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-07 01:33:56 (5209) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-07 01:33:56 (5209) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-07 01:33:56 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-07 01:33:56 (5209) [INFO] Trying other mirror.
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-07 01:33:56 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-07 01:33:56 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-07 01:33:56 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-07 01:33:56 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-07 01:33:56 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-07 01:33:56 (5209) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-07 01:33:56 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-07 01:33:56 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-07 01:33:56 (5209) [INFO]         or
* 2024-03-07 01:33:56 (5209) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-07 01:33:56 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-07 01:33:56 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-07 01:33:56 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-07 01:33:56 (5209) [INFO]         compromise:
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-07 01:33:56 (5209) [INFO] 
* 2024-03-07 01:33:56 (5209) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-07 01:33:56 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-07 01:33:56 (5209) [INFO] Is this ok
* 2024-03-07 01:33:56 (5209) [INFO] [y/N]:
* 2024-03-07 01:33:56 (5226) [INFO] 
* 2024-03-07 01:33:56 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-07 01:33:57 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-07 01:33:57 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-07 01:33:57 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-07 01:33:57 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-07 01:33:57 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-07 01:33:57 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-07 01:33:57 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-07 01:33:57 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-07 01:33:57 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-07 01:34:02 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-07 01:34:02 (1701) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-07 01:34:02 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-07 01:34:02 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_XdcfpyDE8/ea_profile.json
* 2024-03-07 01:34:26 (339) [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/_XdcfpyDE8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-07 01:34:26 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-08 01:33:46 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-08 01:33:46 (1986) [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-03-08 01:33:46 (190) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-03-08 01:33:46 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-08 01:33:47 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-08 01:33:47 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-08 01:33:47 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-08 01:33:47 (5196) [INFO] 
* 2024-03-08 01:33:47 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-08 01:33:47 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 195769.
* 2024-03-08 01:33:47 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-08 01:33:47 (5209) [INFO]   The other application is: yum
* 2024-03-08 01:33:47 (5209) [INFO]     Memory :  35 M RSS (2.9 GB VSZ)
* 2024-03-08 01:33:47 (5209) [INFO]     Started: Fri Mar  8 01:33:43 2024 - 00:04 ago
* 2024-03-08 01:33:47 (5209) [INFO]     State  : Sleeping, pid: 195769
* 2024-03-08 01:33:49 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-08 01:33:49 (5209) [INFO]   The other application is: yum
* 2024-03-08 01:33:49 (5209) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-03-08 01:33:49 (5209) [INFO]     Started: Fri Mar  8 01:33:43 2024 - 00:06 ago
* 2024-03-08 01:33:49 (5209) [INFO]     State  : Sleeping, pid: 195769
* 2024-03-08 01:33:51 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 196116.
* 2024-03-08 01:33:51 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-08 01:33:51 (5209) [INFO]   The other application is: yum
* 2024-03-08 01:33:51 (5209) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-03-08 01:33:51 (5209) [INFO]     Started: Fri Mar  8 01:33:49 2024 - 00:02 ago
* 2024-03-08 01:33:51 (5209) [INFO]     State  : Sleeping, pid: 196116
* 2024-03-08 01:33:53 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-08 01:33:53 (5209) [INFO]   The other application is: yum
* 2024-03-08 01:33:53 (5209) [INFO]     Memory :  38 M RSS (1.1 GB VSZ)
* 2024-03-08 01:33:53 (5209) [INFO]     Started: Fri Mar  8 01:33:49 2024 - 00:04 ago
* 2024-03-08 01:33:53 (5209) [INFO]     State  : Sleeping, pid: 196116
* 2024-03-08 01:33:55 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-08 01:33:55 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-08 01:33:55 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-08 01:33:55 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-08 01:33:55 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-08 01:33:55 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-08 01:33:55 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-08 01:33:55 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-08 01:33:55 (5209) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-03-08 01:33:55 (5226) [INFO] 
* 2024-03-08 01:33:55 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-08 01:33:55 (5196) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-08 01:34:02 (5209) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-08 01:34:02 (5209) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-08 01:34:02 (5209) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-08 01:34:02 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-08 01:34:02 (5209) [INFO] Trying other mirror.
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-08 01:34:02 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-08 01:34:02 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-08 01:34:02 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-08 01:34:02 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-08 01:34:02 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-08 01:34:02 (5209) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-08 01:34:02 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-08 01:34:02 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-08 01:34:02 (5209) [INFO]         or
* 2024-03-08 01:34:02 (5209) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-08 01:34:02 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-08 01:34:02 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-08 01:34:02 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-08 01:34:02 (5209) [INFO]         compromise:
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-08 01:34:02 (5209) [INFO] 
* 2024-03-08 01:34:02 (5209) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-08 01:34:02 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-08 01:34:02 (5209) [INFO] Is this ok
* 2024-03-08 01:34:02 (5209) [INFO] [y/N]:
* 2024-03-08 01:34:02 (5226) [INFO] 
* 2024-03-08 01:34:02 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-08 01:34:05 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-08 01:34:05 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-08 01:34:05 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-08 01:34:05 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-08 01:34:05 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-08 01:34:05 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-08 01:34:05 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-08 01:34:05 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-08 01:34:05 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-08 01:34:09 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-08 01:34:09 (1701) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-08 01:34:09 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-08 01:34:09 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/s1frD_SxUu/ea_profile.json
* 2024-03-08 01:34:12 (339) [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/s1frD_SxUu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-08 01:34:12 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-09 01:34:52 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-09 01:34:52 (1986) [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-03-09 01:34:52 (190) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-03-09 01:34:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-09 01:34:52 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-09 01:34:53 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-09 01:34:53 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-09 01:34:53 (5196) [INFO] 
* 2024-03-09 01:34:53 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-09 01:34:53 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 513454.
* 2024-03-09 01:34:53 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:34:53 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:34:53 (5209) [INFO]     Memory :  35 M RSS (2.8 GB VSZ)
* 2024-03-09 01:34:53 (5209) [INFO]     Started: Sat Mar  9 01:34:48 2024 - 00:05 ago
* 2024-03-09 01:34:53 (5209) [INFO]     State  : Sleeping, pid: 513454
* 2024-03-09 01:34:55 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:34:55 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:34:55 (5209) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-03-09 01:34:55 (5209) [INFO]     Started: Sat Mar  9 01:34:48 2024 - 00:07 ago
* 2024-03-09 01:34:55 (5209) [INFO]     State  : Sleeping, pid: 513454
* 2024-03-09 01:34:57 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:34:57 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:34:57 (5209) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-03-09 01:34:57 (5209) [INFO]     Started: Sat Mar  9 01:34:48 2024 - 00:09 ago
* 2024-03-09 01:34:57 (5209) [INFO]     State  : Sleeping, pid: 513454
* 2024-03-09 01:34:59 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 513900.
* 2024-03-09 01:34:59 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:34:59 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:34:59 (5209) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-03-09 01:34:59 (5209) [INFO]     Started: Sat Mar  9 01:34:57 2024 - 00:02 ago
* 2024-03-09 01:34:59 (5209) [INFO]     State  : Sleeping, pid: 513900
* 2024-03-09 01:35:01 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:35:01 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:35:01 (5209) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-03-09 01:35:01 (5209) [INFO]     Started: Sat Mar  9 01:34:57 2024 - 00:04 ago
* 2024-03-09 01:35:01 (5209) [INFO]     State  : Sleeping, pid: 513900
* 2024-03-09 01:35:03 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:35:03 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:35:03 (5209) [INFO]     Memory :  38 M RSS (996 MB VSZ)
* 2024-03-09 01:35:03 (5209) [INFO]     Started: Sat Mar  9 01:34:57 2024 - 00:06 ago
* 2024-03-09 01:35:03 (5209) [INFO]     State  : Uninterruptible, pid: 513900
* 2024-03-09 01:35:05 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:35:05 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:35:05 (5209) [INFO]     Memory :  39 M RSS (997 MB VSZ)
* 2024-03-09 01:35:05 (5209) [INFO]     Started: Sat Mar  9 01:34:57 2024 - 00:08 ago
* 2024-03-09 01:35:05 (5209) [INFO]     State  : Sleeping, pid: 513900
* 2024-03-09 01:35:07 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-09 01:35:07 (5209) [INFO]   The other application is: yum
* 2024-03-09 01:35:07 (5209) [INFO]     Memory :  39 M RSS (997 MB VSZ)
* 2024-03-09 01:35:07 (5209) [INFO]     Started: Sat Mar  9 01:34:57 2024 - 00:10 ago
* 2024-03-09 01:35:07 (5209) [INFO]     State  : Sleeping, pid: 513900
* 2024-03-09 01:35:09 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-09 01:35:09 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-09 01:35:09 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-09 01:35:09 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-09 01:35:09 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-09 01:35:09 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-09 01:35:09 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-09 01:35:09 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-09 01:35:09 (5209) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-03-09 01:35:09 (5226) [INFO] 
* 2024-03-09 01:35:09 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-09 01:35:09 (5196) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-09 01:35:16 (5209) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-09 01:35:16 (5209) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-09 01:35:16 (5209) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-09 01:35:16 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-09 01:35:16 (5209) [INFO] Trying other mirror.
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-09 01:35:16 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-09 01:35:16 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-09 01:35:16 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-09 01:35:16 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-09 01:35:16 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-09 01:35:16 (5209) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-09 01:35:16 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-09 01:35:16 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-09 01:35:16 (5209) [INFO]         or
* 2024-03-09 01:35:16 (5209) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-09 01:35:16 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-09 01:35:16 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-09 01:35:16 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-09 01:35:16 (5209) [INFO]         compromise:
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-09 01:35:16 (5209) [INFO] 
* 2024-03-09 01:35:16 (5209) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-09 01:35:16 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-09 01:35:16 (5209) [INFO] Is this ok
* 2024-03-09 01:35:16 (5209) [INFO] [y/N]:
* 2024-03-09 01:35:16 (5226) [INFO] 
* 2024-03-09 01:35:16 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-09 01:35:18 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-09 01:35:18 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-09 01:35:18 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-09 01:35:18 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-09 01:35:18 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-09 01:35:18 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-09 01:35:18 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-09 01:35:18 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-09 01:35:18 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-09 01:35:22 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-09 01:35:22 (1701) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-09 01:35:22 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-09 01:35:23 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Wi4AxeTzpF/ea_profile.json
* 2024-03-09 01:35:27 (339) [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/Wi4AxeTzpF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-09 01:35:27 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-10 01:34:46 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-10 01:34:46 (1986) [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-03-10 01:34:46 (190) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-03-10 01:34:46 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-10 01:34:46 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-10 01:34:47 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-10 01:34:47 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-10 01:34:47 (5196) [INFO] 
* 2024-03-10 01:34:47 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-10 01:34:47 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 855827.
* 2024-03-10 01:34:47 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-10 01:34:47 (5209) [INFO]   The other application is: yum
* 2024-03-10 01:34:47 (5209) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-03-10 01:34:47 (5209) [INFO]     Started: Sun Mar 10 01:34:43 2024 - 00:04 ago
* 2024-03-10 01:34:47 (5209) [INFO]     State  : Sleeping, pid: 855827
* 2024-03-10 01:34:49 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-10 01:34:49 (5209) [INFO]   The other application is: yum
* 2024-03-10 01:34:49 (5209) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-03-10 01:34:49 (5209) [INFO]     Started: Sun Mar 10 01:34:43 2024 - 00:06 ago
* 2024-03-10 01:34:49 (5209) [INFO]     State  : Sleeping, pid: 855827
* 2024-03-10 01:34:51 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-10 01:34:51 (5209) [INFO]   The other application is: yum
* 2024-03-10 01:34:51 (5209) [INFO]     Memory :  36 M RSS (2.8 GB VSZ)
* 2024-03-10 01:34:51 (5209) [INFO]     Started: Sun Mar 10 01:34:43 2024 - 00:08 ago
* 2024-03-10 01:34:51 (5209) [INFO]     State  : Sleeping, pid: 855827
* 2024-03-10 01:34:53 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-10 01:34:53 (5209) [INFO]   The other application is: yum
* 2024-03-10 01:34:53 (5209) [INFO]     Memory :  36 M RSS (2.8 GB VSZ)
* 2024-03-10 01:34:53 (5209) [INFO]     Started: Sun Mar 10 01:34:43 2024 - 00:10 ago
* 2024-03-10 01:34:53 (5209) [INFO]     State  : Sleeping, pid: 855827
* 2024-03-10 01:34:55 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-10 01:34:55 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-10 01:34:55 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-10 01:34:55 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-10 01:34:55 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-10 01:34:55 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-10 01:34:55 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-10 01:34:55 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-10 01:34:55 (5209) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-03-10 01:34:55 (5226) [INFO] 
* 2024-03-10 01:34:55 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-10 01:34:55 (5196) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-10 01:35:07 (5209) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-10 01:35:07 (5209) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-10 01:35:07 (5209) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-10 01:35:07 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-10 01:35:07 (5209) [INFO] Trying other mirror.
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-10 01:35:07 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-10 01:35:07 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-10 01:35:07 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-10 01:35:07 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-10 01:35:07 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-10 01:35:07 (5209) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-10 01:35:07 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-10 01:35:07 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-10 01:35:07 (5209) [INFO]         or
* 2024-03-10 01:35:07 (5209) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-10 01:35:07 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-10 01:35:07 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-10 01:35:07 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-10 01:35:07 (5209) [INFO]         compromise:
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-10 01:35:07 (5209) [INFO] 
* 2024-03-10 01:35:07 (5209) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-10 01:35:07 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-10 01:35:07 (5209) [INFO] Is this ok
* 2024-03-10 01:35:07 (5209) [INFO] [y/N]:
* 2024-03-10 01:35:07 (5226) [INFO] 
* 2024-03-10 01:35:07 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-10 01:35:12 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-10 01:35:12 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-10 01:35:12 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-10 01:35:12 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-10 01:35:12 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-10 01:35:12 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-10 01:35:12 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-10 01:35:12 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-10 01:35:12 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-10 01:35:15 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-10 01:35:15 (1701) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-10 01:35:15 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-10 01:35:15 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fPA8MAn_k1/ea_profile.json
* 2024-03-10 01:35:19 (339) [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/fPA8MAn_k1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-10 01:35:19 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-11 01:33:49 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-11 01:33:49 (1986) [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-03-11 01:33:49 (190) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-03-11 01:33:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-11 01:33:49 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-11 01:33:50 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-11 01:33:50 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-11 01:33:50 (5196) [INFO] 
* 2024-03-11 01:33:50 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-11 01:33:50 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 111948.
* 2024-03-11 01:33:50 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-11 01:33:50 (5209) [INFO]   The other application is: yum
* 2024-03-11 01:33:50 (5209) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-03-11 01:33:50 (5209) [INFO]     Started: Mon Mar 11 01:33:46 2024 - 00:04 ago
* 2024-03-11 01:33:50 (5209) [INFO]     State  : Sleeping, pid: 111948
* 2024-03-11 01:33:52 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-11 01:33:52 (5209) [INFO]   The other application is: yum
* 2024-03-11 01:33:52 (5209) [INFO]     Memory :  35 M RSS (2.7 GB VSZ)
* 2024-03-11 01:33:52 (5209) [INFO]     Started: Mon Mar 11 01:33:46 2024 - 00:06 ago
* 2024-03-11 01:33:52 (5209) [INFO]     State  : Sleeping, pid: 111948
* 2024-03-11 01:33:54 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-11 01:33:54 (5209) [INFO]   The other application is: yum
* 2024-03-11 01:33:54 (5209) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-03-11 01:33:54 (5209) [INFO]     Started: Mon Mar 11 01:33:46 2024 - 00:08 ago
* 2024-03-11 01:33:54 (5209) [INFO]     State  : Sleeping, pid: 111948
* 2024-03-11 01:33:56 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-11 01:33:56 (5209) [INFO]   The other application is: yum
* 2024-03-11 01:33:56 (5209) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-11 01:33:56 (5209) [INFO]     Started: Mon Mar 11 01:33:46 2024 - 00:10 ago
* 2024-03-11 01:33:56 (5209) [INFO]     State  : Sleeping, pid: 111948
* 2024-03-11 01:33:58 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 112317.
* 2024-03-11 01:33:58 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-11 01:33:58 (5209) [INFO]   The other application is: yum
* 2024-03-11 01:33:58 (5209) [INFO]     Memory :  37 M RSS (1.4 GB VSZ)
* 2024-03-11 01:33:58 (5209) [INFO]     Started: Mon Mar 11 01:33:55 2024 - 00:03 ago
* 2024-03-11 01:33:58 (5209) [INFO]     State  : Sleeping, pid: 112317
* 2024-03-11 01:34:00 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-11 01:34:00 (5209) [INFO]   The other application is: yum
* 2024-03-11 01:34:00 (5209) [INFO]     Memory :  38 M RSS (1.4 GB VSZ)
* 2024-03-11 01:34:00 (5209) [INFO]     Started: Mon Mar 11 01:33:55 2024 - 00:05 ago
* 2024-03-11 01:34:00 (5209) [INFO]     State  : Sleeping, pid: 112317
* 2024-03-11 01:34:02 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-11 01:34:02 (5209) [INFO]   The other application is: yum
* 2024-03-11 01:34:02 (5209) [INFO]     Memory :  39 M RSS (1.4 GB VSZ)
* 2024-03-11 01:34:02 (5209) [INFO]     Started: Mon Mar 11 01:33:55 2024 - 00:07 ago
* 2024-03-11 01:34:02 (5209) [INFO]     State  : Sleeping, pid: 112317
* 2024-03-11 01:34:04 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-11 01:34:04 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-11 01:34:04 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-11 01:34:04 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-11 01:34:04 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-11 01:34:04 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-11 01:34:04 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-11 01:34:04 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-11 01:34:04 (5209) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-03-11 01:34:04 (5226) [INFO] 
* 2024-03-11 01:34:04 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-11 01:34:04 (5196) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-11 01:34:13 (5209) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-11 01:34:13 (5209) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-11 01:34:13 (5209) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-11 01:34:13 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-11 01:34:13 (5209) [INFO] Trying other mirror.
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-11 01:34:13 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-11 01:34:13 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-11 01:34:13 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-11 01:34:13 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-11 01:34:13 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-11 01:34:13 (5209) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-11 01:34:13 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-11 01:34:13 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-11 01:34:13 (5209) [INFO]         or
* 2024-03-11 01:34:13 (5209) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-11 01:34:13 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-11 01:34:13 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-11 01:34:13 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-11 01:34:13 (5209) [INFO]         compromise:
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-11 01:34:13 (5209) [INFO] 
* 2024-03-11 01:34:13 (5209) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-11 01:34:13 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-11 01:34:13 (5209) [INFO] Is this ok
* 2024-03-11 01:34:13 (5209) [INFO] [y/N]:
* 2024-03-11 01:34:13 (5226) [INFO] 
* 2024-03-11 01:34:13 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-11 01:34:14 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-11 01:34:14 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-11 01:34:14 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-11 01:34:14 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-11 01:34:14 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-11 01:34:14 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-11 01:34:14 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-11 01:34:14 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-11 01:34:14 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-11 01:34:23 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-11 01:34:23 (1701) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-11 01:34:23 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-11 01:34:23 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ccwscHN6lR/ea_profile.json
* 2024-03-11 01:34:29 (339) [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/ccwscHN6lR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-11 01:34:29 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-12 01:33:35 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-12 01:33:35 (1986) [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-03-12 01:33:35 (190) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-03-12 01:33:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-12 01:33:35 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-12 01:33:36 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-12 01:33:36 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-12 01:33:36 (5196) [INFO] 
* 2024-03-12 01:33:36 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-12 01:33:36 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 444758.
* 2024-03-12 01:33:36 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-12 01:33:36 (5209) [INFO]   The other application is: yum
* 2024-03-12 01:33:36 (5209) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-03-12 01:33:36 (5209) [INFO]     Started: Tue Mar 12 01:33:31 2024 - 00:05 ago
* 2024-03-12 01:33:36 (5209) [INFO]     State  : Sleeping, pid: 444758
* 2024-03-12 01:33:38 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-12 01:33:38 (5209) [INFO]   The other application is: yum
* 2024-03-12 01:33:38 (5209) [INFO]     Memory :  37 M RSS (2.9 GB VSZ)
* 2024-03-12 01:33:38 (5209) [INFO]     Started: Tue Mar 12 01:33:31 2024 - 00:07 ago
* 2024-03-12 01:33:38 (5209) [INFO]     State  : Sleeping, pid: 444758
* 2024-03-12 01:33:40 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-12 01:33:40 (5209) [INFO]   The other application is: yum
* 2024-03-12 01:33:40 (5209) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-03-12 01:33:40 (5209) [INFO]     Started: Tue Mar 12 01:33:31 2024 - 00:09 ago
* 2024-03-12 01:33:40 (5209) [INFO]     State  : Sleeping, pid: 444758
* 2024-03-12 01:33:42 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-12 01:33:42 (5209) [INFO]   The other application is: yum
* 2024-03-12 01:33:42 (5209) [INFO]     Memory :  37 M RSS (2.7 GB VSZ)
* 2024-03-12 01:33:42 (5209) [INFO]     Started: Tue Mar 12 01:33:31 2024 - 00:11 ago
* 2024-03-12 01:33:42 (5209) [INFO]     State  : Sleeping, pid: 444758
* 2024-03-12 01:33:44 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 445222.
* 2024-03-12 01:33:44 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-12 01:33:44 (5209) [INFO]   The other application is: yum
* 2024-03-12 01:33:44 (5209) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-03-12 01:33:44 (5209) [INFO]     Started: Tue Mar 12 01:33:43 2024 - 00:01 ago
* 2024-03-12 01:33:44 (5209) [INFO]     State  : Sleeping, pid: 445222
* 2024-03-12 01:33:46 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-12 01:33:46 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-12 01:33:46 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-12 01:33:46 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-12 01:33:46 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-12 01:33:46 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-12 01:33:46 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-12 01:33:46 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-12 01:33:46 (5209) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-03-12 01:33:46 (5226) [INFO] 
* 2024-03-12 01:33:46 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-12 01:33:46 (5196) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]  One of the configured repositories failed (Unknown),
* 2024-03-12 01:33:50 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-12 01:33:50 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-12 01:33:50 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-12 01:33:50 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-12 01:33:50 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-12 01:33:50 (5209) [INFO]             yum --disablerepo=<repoid> ...
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-12 01:33:50 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-12 01:33:50 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]             yum-config-manager --disable <repoid>
* 2024-03-12 01:33:50 (5209) [INFO]         or
* 2024-03-12 01:33:50 (5209) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-12 01:33:50 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-12 01:33:50 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-12 01:33:50 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-12 01:33:50 (5209) [INFO]         compromise:
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2024-03-12 01:33:50 (5209) [INFO]     * free   0 
* 2024-03-12 01:33:50 (5209) [INFO]     * needed 100 k
* 2024-03-12 01:33:50 (5209) [INFO] 
* 2024-03-12 01:33:50 (5226) [INFO] 
* 2024-03-12 01:33:50 (1940) [INFO] Checking /scripts/sysup
* 2024-03-12 01:33:50 (5195) [INFO] Running: /scripts/sysup
* 2024-03-12 01:33:50 (5196) [INFO] 
* 2024-03-12 01:33:50 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-12 01:33:51 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-12 01:33:51 (5226) [INFO] 
* 2024-03-12 01:33:52 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-12 01:33:52 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-12 01:33:52 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-12 01:33:52 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-12 01:33:52 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-12 01:33:52 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-12 01:33:52 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-12 01:33:52 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-12 01:33:52 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-12 01:33:55 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-12 01:33:55 (1701) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-03-12 01:33:55 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-12 01:33:55 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F1OwDsK54w/ea_profile.json
* 2024-03-12 01:33:56 (339) [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/F1OwDsK54w/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-12 01:33:56 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-13 01:34:05 (190) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-13 01:34:05 (1986) [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-03-13 01:34:09 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-13 01:34:10 (190) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-13 01:34:10 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-13 01:34:10 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-13 01:34:10 (5196) [INFO] 
* 2024-03-13 01:34:10 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-13 01:34:10 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 915213.
* 2024-03-13 01:34:10 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-13 01:34:10 (5209) [INFO]   The other application is: yum
* 2024-03-13 01:34:10 (5209) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-03-13 01:34:10 (5209) [INFO]     Started: Wed Mar 13 01:34:03 2024 - 00:07 ago
* 2024-03-13 01:34:10 (5209) [INFO]     State  : Sleeping, pid: 915213
* 2024-03-13 01:34:12 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-13 01:34:12 (5209) [INFO]   The other application is: yum
* 2024-03-13 01:34:12 (5209) [INFO]     Memory :  36 M RSS (2.7 GB VSZ)
* 2024-03-13 01:34:12 (5209) [INFO]     Started: Wed Mar 13 01:34:03 2024 - 00:09 ago
* 2024-03-13 01:34:12 (5209) [INFO]     State  : Sleeping, pid: 915213
* 2024-03-13 01:34:14 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-03-13 01:34:14 (5209) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-03-13 01:34:14 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-13 01:34:14 (5209) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-03-13 01:34:14 (5209) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-03-13 01:34:14 (5209) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-03-13 01:34:14 (5209) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-03-13 01:34:14 (5209) [INFO] Cleaning up list of fastest mirrors
* 2024-03-13 01:34:14 (5209) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-03-13 01:34:14 (5226) [INFO] 
* 2024-03-13 01:34:14 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-13 01:34:14 (5196) [INFO] 
* 2024-03-13 01:34:15 (5209) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 915690.
* 2024-03-13 01:34:15 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-13 01:34:15 (5209) [INFO]   The other application is: yum
* 2024-03-13 01:34:15 (5209) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-03-13 01:34:15 (5209) [INFO]     Started: Wed Mar 13 01:34:12 2024 - 00:03 ago
* 2024-03-13 01:34:15 (5209) [INFO]     State  : Sleeping, pid: 915690
* 2024-03-13 01:34:17 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-13 01:34:17 (5209) [INFO]   The other application is: yum
* 2024-03-13 01:34:17 (5209) [INFO]     Memory :  38 M RSS (3.1 GB VSZ)
* 2024-03-13 01:34:17 (5209) [INFO]     Started: Wed Mar 13 01:34:12 2024 - 00:05 ago
* 2024-03-13 01:34:17 (5209) [INFO]     State  : Sleeping, pid: 915690
* 2024-03-13 01:34:19 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-13 01:34:19 (5209) [INFO]   The other application is: yum
* 2024-03-13 01:34:19 (5209) [INFO]     Memory :  38 M RSS (2.7 GB VSZ)
* 2024-03-13 01:34:19 (5209) [INFO]     Started: Wed Mar 13 01:34:12 2024 - 00:07 ago
* 2024-03-13 01:34:19 (5209) [INFO]     State  : Sleeping, pid: 915690
* 2024-03-13 01:34:21 (5209) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-03-13 01:34:21 (5209) [INFO]   The other application is: yum
* 2024-03-13 01:34:21 (5209) [INFO]     Memory :  39 M RSS (2.7 GB VSZ)
* 2024-03-13 01:34:21 (5209) [INFO]     Started: Wed Mar 13 01:34:12 2024 - 00:09 ago
* 2024-03-13 01:34:21 (5209) [INFO]     State  : Sleeping, pid: 915690
* 2024-03-13 01:34:27 (5209) [INFO] Importing GPG key 0x98AB5139:
* 2024-03-13 01:34:27 (5209) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-03-13 01:34:27 (5209) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-03-13 01:34:27 (5209) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-03-13 01:34:27 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-13 01:34:27 (5209) [INFO] Trying other mirror.
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-03-13 01:34:27 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-13 01:34:27 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-13 01:34:27 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-13 01:34:27 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-13 01:34:27 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-13 01:34:27 (5209) [INFO]             yum --disablerepo=virtualbox ...
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-13 01:34:27 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-13 01:34:27 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]             yum-config-manager --disable virtualbox
* 2024-03-13 01:34:27 (5209) [INFO]         or
* 2024-03-13 01:34:27 (5209) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-13 01:34:27 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-13 01:34:27 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-13 01:34:27 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-13 01:34:27 (5209) [INFO]         compromise:
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-03-13 01:34:27 (5209) [INFO] 
* 2024-03-13 01:34:27 (5209) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-03-13 01:34:27 (5209) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-13 01:34:27 (5209) [INFO] Is this ok
* 2024-03-13 01:34:27 (5209) [INFO] [y/N]:
* 2024-03-13 01:34:27 (5226) [INFO] 
* 2024-03-13 01:34:27 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-13 01:34:28 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-13 01:34:28 (1818) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-13 01:34:28 (1818) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-13 01:34:28 (1796) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-13 01:34:28 (1796) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-13 01:34:28 (1818) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-13 01:34:28 (1818) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-13 01:34:28 (1796) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-13 01:34:28 (1818) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-13 01:34:33 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-13 01:34:33 (1701) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-13 01:34:33 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-13 01:34:33 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ti08cA8Pns/ea_profile.json
* 2024-03-13 01:34:45 (339) [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/Ti08cA8Pns/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-13 01:34:45 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-14 01:33:53 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-14 01:33:53 (1947) [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-03-14 01:33:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-14 01:33:53 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-14 01:34:14 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-14 01:34:14 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-14 01:34:14 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-14 01:34:14 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-14 01:34:14 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-14 01:34:14 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-14 01:34:14 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-14 01:34:14 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-14 01:34:14 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-14 01:34:23 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-14 01:34:23 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-14 01:34:23 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-14 01:34:23 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/scnfRwinhx/ea_profile.json
* 2024-03-14 01:34:33 (340) [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/scnfRwinhx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-14 01:34:33 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-15 01:34:11 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-15 01:34:11 (1947) [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-03-15 01:34:11 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-15 01:34:11 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-15 01:34:13 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-15 01:34:13 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-15 01:34:13 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-15 01:34:13 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-15 01:34:13 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-15 01:34:13 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-15 01:34:13 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-15 01:34:13 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-15 01:34:13 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-15 01:34:37 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-15 01:34:37 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-15 01:34:37 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-15 01:34:37 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MA4gnzUO9O/ea_profile.json
* 2024-03-15 01:35:41 (340) [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/MA4gnzUO9O/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-15 01:35:41 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-16 01:36:23 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-16 01:36:23 (1947) [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-03-16 01:36:23 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-16 01:36:23 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-16 01:36:35 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-16 01:36:35 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-16 01:36:35 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-16 01:36:35 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-16 01:36:35 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-16 01:36:35 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-16 01:36:35 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-16 01:36:35 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-16 01:36:35 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-16 01:36:39 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-16 01:36:39 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-16 01:36:39 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-16 01:36:39 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L3uQnWrD8w/ea_profile.json
* 2024-03-16 01:36:43 (340) [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/L3uQnWrD8w/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-16 01:36:43 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-17 01:35:31 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-17 01:35:31 (1947) [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-03-17 01:35:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-17 01:35:32 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-17 01:35:45 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-17 01:35:45 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-17 01:35:45 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-17 01:35:45 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-17 01:35:45 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-17 01:35:45 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-17 01:35:45 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-17 01:35:45 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-17 01:35:45 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-17 01:35:49 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-17 01:35:49 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-17 01:35:49 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-17 01:35:49 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tvJGHbxLJf/ea_profile.json
* 2024-03-17 01:35:53 (340) [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/tvJGHbxLJf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-17 01:35:53 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-18 01:33:59 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-18 01:33:59 (1947) [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-03-18 01:34:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-18 01:34:00 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-18 01:34:07 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-18 01:34:07 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-18 01:34:07 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-18 01:34:07 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-18 01:34:07 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-18 01:34:07 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-18 01:34:07 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-18 01:34:07 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-18 01:34:07 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-18 01:34:16 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-18 01:34:16 (1717) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 675121.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (325 MB VSZ)
    Started: Mon Mar 18 01:34:06 2024 - 00:01 ago
    State  : Sleeping, pid: 675121
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Mon Mar 18 01:34:06 2024 - 00:03 ago
    State  : Sleeping, pid: 675121
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Mon Mar 18 01:34:06 2024 - 00:05 ago
    State  : Sleeping, pid: 675121
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-18 01:34:17 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-18 01:34:17 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EqM8EsMQ5_/ea_profile.json
* 2024-03-18 01:34:20 (340) [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/EqM8EsMQ5_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-18 01:34:20 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-19 01:34:56 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-19 01:34:56 (1947) [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-03-19 01:34:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-19 01:34:57 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-19 01:35:22 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-19 01:35:22 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-19 01:35:22 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-19 01:35:22 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-19 01:35:22 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-19 01:35:22 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-19 01:35:22 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-19 01:35:22 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-19 01:35:22 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-19 01:35:43 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-19 01:35:43 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-19 01:35:44 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-19 01:35:44 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pIlhYANuFJ/ea_profile.json
* 2024-03-19 01:36:02 (340) [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/pIlhYANuFJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-19 01:36:02 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-20 01:34:25 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-20 01:34:25 (1947) [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-03-20 01:34:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-20 01:34:26 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-20 01:34:32 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-20 01:34:32 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-20 01:34:32 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-20 01:34:32 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-20 01:34:32 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-20 01:34:32 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-20 01:34:32 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-20 01:34:32 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-20 01:34:32 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-20 01:34:41 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-20 01:34:41 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-20 01:34:42 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-20 01:34:42 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mQjTqbxlNu/ea_profile.json
* 2024-03-20 01:34:51 (340) [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/mQjTqbxlNu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-20 01:34:51 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-21 01:34:05 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-21 01:34:05 (1947) [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-03-21 01:34:06 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-21 01:34:06 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-21 01:34:18 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-21 01:34:18 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-21 01:34:18 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-21 01:34:18 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-21 01:34:18 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-21 01:34:18 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-21 01:34:18 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-21 01:34:18 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-21 01:34:18 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-21 01:34:53 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-21 01:34:53 (1717) [ERROR] https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-21 01:34:53 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-21 01:34:53 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kKjT5kYzRy/ea_profile.json
* 2024-03-21 01:34:58 (340) [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/kKjT5kYzRy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-21 01:34:58 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-22 01:34:27 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-22 01:34:27 (1947) [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-03-22 01:34:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-22 01:34:29 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-22 01:34:34 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-22 01:34:34 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-22 01:34:34 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-22 01:34:34 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-22 01:34:34 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-22 01:34:34 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-22 01:34:34 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-22 01:34:34 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-22 01:34:34 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-22 01:35:09 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-22 01:35:09 (1717) [ERROR] https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-22 01:35:09 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-22 01:35:09 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8tBMqUQKBH/ea_profile.json
* 2024-03-22 01:35:12 (340) [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/8tBMqUQKBH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-22 01:35:12 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-23 01:34:47 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-23 01:34:47 (1947) [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-03-23 01:34:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-23 01:34:49 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-23 01:35:00 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-23 01:35:00 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-23 01:35:00 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-23 01:35:00 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-23 01:35:00 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-23 01:35:00 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-23 01:35:00 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-23 01:35:00 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-23 01:35:00 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-23 01:35:03 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-23 01:35:03 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-23 01:35:04 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-23 01:35:04 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/E048DkGkbR/ea_profile.json
* 2024-03-23 01:35:09 (340) [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/E048DkGkbR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-23 01:35:09 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-24 01:35:49 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-24 01:35:49 (1947) [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-03-24 01:35:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-24 01:35:50 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-24 01:36:57 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-24 01:36:57 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-24 01:36:57 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-24 01:36:57 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-24 01:36:57 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-24 01:36:57 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-24 01:36:57 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-24 01:36:57 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-24 01:36:57 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-24 01:37:11 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-24 01:37:11 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-24 01:37:11 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-24 01:37:11 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oyB_0iPtj7/ea_profile.json
* 2024-03-24 01:38:22 (340) [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/oyB_0iPtj7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-24 01:38:22 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-25 01:35:03 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-25 01:35:03 (1947) [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-03-25 01:35:03 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-25 01:35:03 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-25 01:35:10 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-25 01:35:10 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-25 01:35:10 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-25 01:35:10 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-25 01:35:10 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-25 01:35:10 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-25 01:35:10 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-25 01:35:10 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-25 01:35:10 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-25 01:35:14 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-25 01:35:14 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-25 01:35:14 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-25 01:35:14 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/smvDFn4mgb/ea_profile.json
* 2024-03-25 01:35:18 (340) [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/smvDFn4mgb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-25 01:35:18 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-26 01:33:57 (191) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-26 01:33:57 (1947) [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-03-26 01:33:57 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-26 01:33:57 (191) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-26 01:35:39 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-26 01:35:39 (1834) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-26 01:35:39 (1834) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-26 01:35:39 (1812) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-26 01:35:39 (1812) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-26 01:35:39 (1834) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-26 01:35:39 (1834) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-26 01:35:39 (1812) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-26 01:35:39 (1834) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-26 01:35:42 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-26 01:35:42 (1717) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-26 01:35:43 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-26 01:35:43 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/svPOJzA5Kz/ea_profile.json
* 2024-03-26 01:35:48 (340) [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/svPOJzA5Kz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-26 01:35:48 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-27 01:34:16 (194) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-27 01:34:16 (1985) [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-03-27 01:34:16 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-27 01:34:17 (194) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-27 01:34:26 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-27 01:34:26 (1872) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-27 01:34:26 (1872) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-27 01:34:26 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-27 01:34:26 (1850) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-27 01:34:26 (1872) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-27 01:34:26 (1872) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-27 01:34:26 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-27 01:34:26 (1872) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-27 01:34:28 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-27 01:34:28 (1755) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-27 01:34:29 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-27 01:34:29 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gDvNc7Xe7a/ea_profile.json
* 2024-03-27 01:34:34 (344) [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/gDvNc7Xe7a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-27 01:34:34 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-28 01:33:58 (194) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-28 01:33:58 (1985) [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-03-28 01:33:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-28 01:33:59 (194) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-28 01:34:02 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-28 01:34:02 (1872) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-28 01:34:02 (1872) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-28 01:34:02 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-28 01:34:02 (1850) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-28 01:34:02 (1872) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-28 01:34:02 (1872) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-28 01:34:02 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-28 01:34:02 (1872) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-28 01:34:07 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-28 01:34:07 (1755) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-28 01:34:07 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-28 01:34:07 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EbohOXwaNr/ea_profile.json
* 2024-03-28 01:34:11 (344) [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/EbohOXwaNr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-28 01:34:11 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-29 01:34:20 (194) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-29 01:34:20 (1985) [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-03-29 01:34:20 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-29 01:34:21 (194) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-29 01:34:31 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-29 01:34:31 (1872) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-29 01:34:31 (1872) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-29 01:34:31 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-29 01:34:31 (1850) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-29 01:34:31 (1872) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-29 01:34:31 (1872) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-29 01:34:31 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-29 01:34:31 (1872) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-29 01:34:35 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-29 01:34:35 (1755) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-29 01:34:35 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-29 01:34:35 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0yxIDus6tD/ea_profile.json
* 2024-03-29 01:34:38 (344) [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/0yxIDus6tD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-29 01:34:38 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-30 01:35:01 (194) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-30 01:35:01 (1985) [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-03-30 01:35:01 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-30 01:35:02 (194) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-30 01:35:13 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-30 01:35:13 (1872) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-30 01:35:13 (1872) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-30 01:35:13 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-30 01:35:13 (1850) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-30 01:35:13 (1872) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-30 01:35:13 (1872) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-30 01:35:13 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-30 01:35:13 (1872) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-30 01:35:16 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-30 01:35:16 (1755) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-30 01:35:16 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-30 01:35:16 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q_1AvrOC32/ea_profile.json
* 2024-03-30 01:35:20 (344) [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/q_1AvrOC32/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-30 01:35:20 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-31 01:35:49 (194) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-03-31 01:35:49 (1985) [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-03-31 01:35:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-03-31 01:35:50 (194) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-03-31 01:36:06 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-03-31 01:36:06 (1872) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-03-31 01:36:06 (1872) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-03-31 01:36:06 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-31 01:36:06 (1850) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-03-31 01:36:06 (1872) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-03-31 01:36:06 (1872) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-03-31 01:36:06 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-03-31 01:36:06 (1872) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-03-31 01:36:09 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-31 01:36:09 (1755) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-03-31 01:36:09 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-31 01:36:09 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Dygqe5Txa0/ea_profile.json
* 2024-03-31 01:36:13 (344) [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/Dygqe5Txa0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-31 01:36:13 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-01 01:33:58 (194) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-01 01:33:58 (1985) [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-04-01 01:33:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-01 01:33:58 (194) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-01 01:34:14 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-01 01:34:14 (1872) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-01 01:34:14 (1872) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-01 01:34:14 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-01 01:34:14 (1850) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-01 01:34:14 (1872) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-01 01:34:14 (1872) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-01 01:34:14 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-01 01:34:14 (1872) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-01 01:34:18 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-01 01:34:18 (1755) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-01 01:34:19 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-01 01:34:19 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/G9DxaAc4G9/ea_profile.json
* 2024-04-01 01:34:22 (344) [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/G9DxaAc4G9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-04-01 01:34:22 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-02 01:33:53 (194) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-02 01:33:53 (1985) [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-04-02 01:33:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-02 01:33:54 (194) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-02 01:34:08 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-02 01:34:08 (1872) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-02 01:34:08 (1872) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-02 01:34:08 (1850) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-02 01:34:08 (1850) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-02 01:34:08 (1872) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-02 01:34:08 (1872) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-02 01:34:08 (1850) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-02 01:34:08 (1872) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-02 01:34:11 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-02 01:34:11 (1755) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-02 01:34:11 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-02 01:34:11 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uvefo0KQgd/ea_profile.json
* 2024-04-02 01:34:16 (344) [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/uvefo0KQgd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-04-02 01:34:16 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-03 01:33:52 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-03 01:33:53 (1990) [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-04-03 01:33:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-03 01:33:53 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-03 01:34:07 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-03 01:34:07 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-03 01:34:07 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-03 01:34:07 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-03 01:34:07 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-03 01:34:07 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-03 01:34:07 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-03 01:34:07 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-03 01:34:07 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-03 01:34:10 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-03 01:34:10 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-03 01:34:10 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-03 01:34:10 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u16i06xyFr/ea_profile.json
* 2024-04-03 01:34:13 (346) [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/u16i06xyFr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-03 01:34:13 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-04 01:33:35 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-04 01:33:35 (1990) [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-04-04 01:33:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-04 01:33:35 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-04 01:33:46 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-04 01:33:46 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-04 01:33:46 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-04 01:33:46 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-04 01:33:46 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-04 01:33:46 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-04 01:33:46 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-04 01:33:46 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-04 01:33:46 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-04 01:33:51 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-04 01:33:51 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-04 01:33:51 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-04 01:33:51 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UJAoP2sfAD/ea_profile.json
* 2024-04-04 01:33:57 (346) [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/UJAoP2sfAD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-04 01:33:57 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-05 01:33:49 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-05 01:33:49 (1990) [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-04-05 01:33:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-05 01:33:49 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-05 01:34:00 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-05 01:34:00 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-05 01:34:00 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-05 01:34:00 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-05 01:34:00 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-05 01:34:00 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-05 01:34:00 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-05 01:34:00 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-05 01:34:00 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-05 01:34:04 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-05 01:34:04 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-05 01:34:05 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-05 01:34:05 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FSPAhNl9iN/ea_profile.json
* 2024-04-05 01:34:09 (346) [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/FSPAhNl9iN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-05 01:34:09 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-06 01:34:44 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-06 01:34:44 (1990) [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-04-06 01:34:44 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-06 01:34:44 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-06 01:34:54 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-06 01:34:54 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-06 01:34:54 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-06 01:34:54 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-06 01:34:54 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-06 01:34:54 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-06 01:34:54 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-06 01:34:54 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-06 01:34:54 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-06 01:34:57 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-06 01:34:57 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-06 01:34:57 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-06 01:34:57 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y6iQYNBPqx/ea_profile.json
* 2024-04-06 01:35:01 (346) [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/Y6iQYNBPqx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-06 01:35:01 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-07 01:34:37 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-07 01:34:37 (1990) [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-04-07 01:34:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-07 01:34:38 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-07 01:34:47 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-07 01:34:47 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-07 01:34:47 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-07 01:34:47 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-07 01:34:47 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-07 01:34:47 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-07 01:34:47 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-07 01:34:47 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-07 01:34:47 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-07 01:34:52 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-07 01:34:52 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-07 01:34:52 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-07 01:34:52 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JjUe3UYlgK/ea_profile.json
* 2024-04-07 01:34:58 (346) [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/JjUe3UYlgK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-07 01:34:58 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-08 01:33:38 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-08 01:33:39 (1990) [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-04-08 01:33:39 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-08 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-08 01:33:39 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-08 01:33:52 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-08 01:33:52 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-08 01:33:52 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-08 01:33:52 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-08 01:33:52 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-08 01:33:52 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-08 01:33:52 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-08 01:33:52 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-08 01:33:52 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-08 01:34:00 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-08 01:34:00 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-08 01:34:00 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-08 01:34:01 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5_B7qnL7nU/ea_profile.json
* 2024-04-08 01:34:07 (346) [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/5_B7qnL7nU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-08 01:34:07 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-09 01:33:35 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-09 01:33:35 (1990) [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-04-09 01:33:35 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-09 01:33:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-09 01:33:36 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-09 01:33:39 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-09 01:33:39 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-09 01:33:39 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-09 01:33:39 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-09 01:33:39 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-09 01:33:39 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-09 01:33:39 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-09 01:33:39 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-09 01:33:39 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-09 01:33:46 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-09 01:33:46 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-09 01:33:46 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-09 01:33:46 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NN1qsss5Zu/ea_profile.json
* 2024-04-09 01:33:48 (346) [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/NN1qsss5Zu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-09 01:33:48 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-10 01:33:54 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-10 01:33:54 (1990) [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-04-10 01:33:54 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-10 01:33:55 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-10 01:33:56 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-10 01:34:05 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-10 01:34:05 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-10 01:34:05 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-10 01:34:05 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-10 01:34:05 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-10 01:34:05 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-10 01:34:05 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-10 01:34:05 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-10 01:34:05 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-10 01:34:10 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-10 01:34:10 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-10 01:34:10 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-10 01:34:10 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WBrvtT4NFK/ea_profile.json
* 2024-04-10 01:34:14 (346) [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/WBrvtT4NFK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-10 01:34:14 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-11 01:33:50 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-11 01:33:50 (1990) [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-04-11 01:33:50 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-11 01:33:50 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-11 01:33:51 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-11 01:33:56 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-11 01:33:56 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-11 01:33:56 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-11 01:33:56 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-11 01:33:56 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-11 01:33:56 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-11 01:33:56 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-11 01:33:56 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-11 01:33:56 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-11 01:34:01 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-11 01:34:01 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-11 01:34:01 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-11 01:34:01 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sQigzLCeZl/ea_profile.json
* 2024-04-11 01:34:08 (346) [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/sQigzLCeZl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-11 01:34:08 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-12 01:33:41 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-12 01:33:41 (1990) [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-04-12 01:33:41 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-12 01:33:41 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-12 01:33:42 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-12 01:33:47 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-12 01:33:47 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-12 01:33:47 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-12 01:33:47 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-12 01:33:47 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-12 01:33:47 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-12 01:33:47 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-12 01:33:47 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-12 01:33:47 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-12 01:33:54 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-12 01:33:54 (1760) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 660182.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  34 M RSS (325 MB VSZ)
    Started: Fri Apr 12 01:33:45 2024 - 00:02 ago
    State  : Sleeping, pid: 660182
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Fri Apr 12 01:33:45 2024 - 00:04 ago
    State  : Sleeping, pid: 660182
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-12 01:33:55 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-12 01:33:55 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1_p2J6UAD3/ea_profile.json
* 2024-04-12 01:34:00 (346) [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/1_p2J6UAD3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-12 01:34:00 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-13 01:34:48 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-13 01:34:48 (1990) [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-04-13 01:34:48 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-13 01:34:48 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-13 01:34:49 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-13 01:34:52 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-13 01:34:52 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-13 01:34:52 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-13 01:34:52 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-13 01:34:52 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-13 01:34:52 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-13 01:34:52 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-13 01:34:52 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-13 01:34:52 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-13 01:34:56 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-13 01:34:56 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-13 01:34:56 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-13 01:34:56 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PSlGnj3geY/ea_profile.json
* 2024-04-13 01:35:00 (346) [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/PSlGnj3geY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-13 01:35:00 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-14 01:35:37 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-14 01:35:37 (1990) [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-04-14 01:35:37 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-14 01:35:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-14 01:35:38 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-14 01:35:45 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-14 01:35:45 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-14 01:35:45 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-14 01:35:45 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-14 01:35:45 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-14 01:35:45 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-14 01:35:45 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-14 01:35:45 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-14 01:35:45 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-14 01:36:18 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-14 01:36:18 (1760) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 421701.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  34 M RSS (325 MB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:02 ago
    State  : Sleeping, pid: 421701
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  37 M RSS (1.2 GB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:04 ago
    State  : Sleeping, pid: 421701
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.2 GB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:06 ago
    State  : Sleeping, pid: 421701
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.2 GB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:08 ago
    State  : Sleeping, pid: 421701
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.2 GB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:10 ago
    State  : Sleeping, pid: 421701
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.2 GB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:12 ago
    State  : Sleeping, pid: 421701
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.2 GB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:14 ago
    State  : Sleeping, pid: 421701
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.2 GB VSZ)
    Started: Sun Apr 14 01:35:43 2024 - 00:16 ago
    State  : Sleeping, pid: 421701
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-14 01:36:18 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-14 01:36:18 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/l_Rv_rcNvq/ea_profile.json
* 2024-04-14 01:36:23 (346) [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/l_Rv_rcNvq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-14 01:36:23 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-15 01:33:37 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-15 01:33:37 (1990) [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-04-15 01:33:37 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-15 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-15 01:33:37 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-15 01:33:45 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-15 01:33:45 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-15 01:33:45 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-15 01:33:45 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-15 01:33:45 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-15 01:33:45 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-15 01:33:45 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-15 01:33:45 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-15 01:33:45 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-15 01:33:49 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-15 01:33:49 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-15 01:33:49 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-15 01:33:49 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/icRqDC1GIi/ea_profile.json
* 2024-04-15 01:33:52 (346) [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/icRqDC1GIi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-15 01:33:52 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-16 01:34:52 (6907) [INFO] Self-update of script version 33 requested.
* 2024-04-16 01:34:52 (6929) [INFO] Script is up to date.
* 2024-04-16 01:34:53 (196) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-16 01:34:53 (1990) [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-04-16 01:34:53 (196) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-04-16 01:34:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-16 01:34:54 (196) [WARN] *** Elevation Blocker detected: ***
You are using MySQL 5.7 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later.

You can update to version 8.0 using the following command:

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

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

* 2024-04-16 01:35:11 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-16 01:35:11 (1877) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-16 01:35:11 (1877) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-16 01:35:11 (1855) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-16 01:35:11 (1855) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-16 01:35:11 (1877) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-16 01:35:11 (1877) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-16 01:35:11 (1855) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-16 01:35:11 (1877) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-16 01:35:16 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-16 01:35:16 (1760) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-16 01:35:16 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-16 01:35:18 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JWPa3uODES/ea_profile.json
* 2024-04-16 01:35:22 (346) [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/JWPa3uODES/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-16 01:35:22 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-17 01:33:41 (6907) [INFO] Self-update of script version 33 requested.
* 2024-04-17 01:33:41 (6912) [INFO] Newer version of script found. Downloading.
* 2024-04-17 01:33:42 (6921) [INFO] Script update to version 34 successful.
* 2024-04-17 01:33:43 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-17 01:33:43 (2007) [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-04-17 01:33:44 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-17 01:33:46 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-17 01:33:46 (719) [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.

* 2024-04-17 01:33:56 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-17 01:33:56 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-17 01:33:56 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-17 01:33:56 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-17 01:33:56 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-17 01:33:56 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-17 01:33:56 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-17 01:33:56 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-17 01:33:56 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-17 01:34:00 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-17 01:34:00 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-17 01:34:00 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-17 01:34:00 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rAgv5lzKHT/ea_profile.json
* 2024-04-17 01:34:04 (342) [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/rAgv5lzKHT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-17 01:34:04 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-18 01:34:04 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-18 01:34:04 (7128) [INFO] Script is up to date.
* 2024-04-18 01:34:06 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-18 01:34:06 (2007) [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-04-18 01:34:10 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-18 01:34:10 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-18 01:34:10 (719) [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.

* 2024-04-18 01:34:18 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-18 01:34:18 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-18 01:34:18 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-18 01:34:18 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-18 01:34:18 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-18 01:34:18 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-18 01:34:18 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-18 01:34:18 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-18 01:34:18 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-18 01:34:22 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-18 01:34:22 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-18 01:34:22 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-18 01:34:22 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jPMJE9Bi27/ea_profile.json
* 2024-04-18 01:34:27 (342) [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/jPMJE9Bi27/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-18 01:34:27 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-19 01:44:34 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-19 01:44:34 (7128) [INFO] Script is up to date.
* 2024-04-19 01:44:35 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-19 01:44:35 (2007) [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-04-19 01:44:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-19 01:44:36 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-19 01:44:36 (719) [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.

* 2024-04-19 01:44:47 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-19 01:44:47 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-19 01:44:47 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-19 01:44:47 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-19 01:44:47 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-19 01:44:47 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-19 01:44:47 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-19 01:44:47 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-19 01:44:47 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-19 01:48:35 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-19 01:48:35 (1777) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 387111.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (325 MB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:02 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:04 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:06 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:08 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:10 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:12 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:14 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:16 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:18 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:20 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:22 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:24 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:26 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:28 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:30 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:32 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:34 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:36 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:38 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:40 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:42 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:44 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:46 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:48 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:50 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:52 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:54 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:56 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 00:58 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:00 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:02 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:04 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:06 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:08 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:10 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:12 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:14 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:16 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:18 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:20 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:22 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:24 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:26 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:28 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:30 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:32 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:34 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:36 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:38 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:40 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:42 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:44 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:46 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:48 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:50 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:52 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:54 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:56 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 01:58 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:00 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:02 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:04 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:06 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:08 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:10 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:12 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:14 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:16 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:18 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:20 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:22 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:24 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:26 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:28 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:30 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:32 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:34 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:36 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:38 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:40 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:42 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:44 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:46 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:48 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:50 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:52 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:54 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:56 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 02:58 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 03:00 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 03:02 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 03:04 ago
    State  : Sleeping, pid: 387111
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (1.1 GB VSZ)
    Started: Fri Apr 19 01:44:45 2024 - 03:06 ago
    State  : Sleeping, pid: 387111
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-19 01:48:35 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-19 01:48:35 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iSK3KR4Gnu/ea_profile.json
* 2024-04-19 01:50:57 (342) [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/iSK3KR4Gnu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-19 01:50:57 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-20 01:35:21 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-20 01:35:21 (7128) [INFO] Script is up to date.
* 2024-04-20 01:35:22 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-20 01:35:22 (2007) [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-04-20 01:35:22 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-20 01:35:23 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-20 01:35:23 (719) [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.

* 2024-04-20 01:35:42 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-20 01:35:42 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-20 01:35:42 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-20 01:35:42 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-20 01:35:42 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-20 01:35:42 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-20 01:35:42 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-20 01:35:42 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-20 01:35:42 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-20 01:35:46 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-20 01:35:46 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-20 01:35:47 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-20 01:35:47 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KeOowto4uH/ea_profile.json
* 2024-04-20 01:35:52 (342) [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/KeOowto4uH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-20 01:35:52 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-21 01:35:37 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-21 01:35:37 (7128) [INFO] Script is up to date.
* 2024-04-21 01:35:38 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-21 01:35:38 (2007) [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-04-21 01:35:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-21 01:35:39 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-21 01:35:39 (719) [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.

* 2024-04-21 01:35:54 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-21 01:35:54 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-21 01:35:54 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-21 01:35:54 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-21 01:35:54 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-21 01:35:54 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-21 01:35:54 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-21 01:35:54 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-21 01:35:54 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-21 01:35:58 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-21 01:35:58 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-21 01:35:58 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-21 01:35:58 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lII1Um0oj0/ea_profile.json
* 2024-04-21 01:36:04 (342) [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/lII1Um0oj0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-21 01:36:04 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-22 01:33:38 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-22 01:33:38 (7128) [INFO] Script is up to date.
* 2024-04-22 01:33:39 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-22 01:33:39 (2007) [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-04-22 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-22 01:33:40 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-22 01:33:40 (719) [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.

* 2024-04-22 01:33:53 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-22 01:33:53 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-22 01:33:53 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-22 01:33:53 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-22 01:33:53 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-22 01:33:53 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-22 01:33:53 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-22 01:33:53 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-22 01:33:53 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-22 01:33:55 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-22 01:33:55 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-22 01:33:56 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-22 01:33:56 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bfaZYX_igJ/ea_profile.json
* 2024-04-22 01:33:58 (342) [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/bfaZYX_igJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-22 01:33:58 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-23 01:33:48 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-23 01:33:48 (7128) [INFO] Script is up to date.
* 2024-04-23 01:33:49 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-23 01:33:49 (2007) [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-04-23 01:33:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-23 01:33:49 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-23 01:33:49 (719) [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.

* 2024-04-23 01:34:01 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-23 01:34:01 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-23 01:34:01 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-23 01:34:01 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-23 01:34:01 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-23 01:34:01 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-23 01:34:01 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-23 01:34:01 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-23 01:34:01 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-23 01:34:06 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-23 01:34:06 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-23 01:34:06 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-23 01:34:06 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_4I703ANKI/ea_profile.json
* 2024-04-23 01:34:11 (342) [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/_4I703ANKI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-23 01:34:11 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-24 01:34:32 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-24 01:34:32 (7128) [INFO] Script is up to date.
* 2024-04-24 01:34:33 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-24 01:34:33 (2007) [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-04-24 01:34:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-24 01:34:34 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-24 01:34:34 (719) [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.

* 2024-04-24 01:34:39 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-24 01:34:39 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-24 01:34:39 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-24 01:34:39 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-24 01:34:39 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-24 01:34:39 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-24 01:34:39 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-24 01:34:39 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-24 01:34:39 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-24 01:34:43 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-24 01:34:43 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-24 01:34:43 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-24 01:34:43 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RsMeDgfuO6/ea_profile.json
* 2024-04-24 01:34:46 (342) [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/RsMeDgfuO6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-24 01:34:46 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-25 01:33:37 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-25 01:33:37 (7128) [INFO] Script is up to date.
* 2024-04-25 01:33:38 (192) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-25 01:33:38 (2007) [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-04-25 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-25 01:33:39 (712) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-25 01:33:39 (719) [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.

* 2024-04-25 01:33:52 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-25 01:33:52 (1894) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-25 01:33:52 (1894) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-25 01:33:52 (1872) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-25 01:33:52 (1872) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-25 01:33:52 (1894) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-25 01:33:52 (1894) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-25 01:33:52 (1872) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-25 01:33:52 (1894) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-25 01:33:55 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-25 01:33:55 (1777) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-25 01:33:56 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-25 01:33:56 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sWpw8Nm3On/ea_profile.json
* 2024-04-25 01:34:02 (342) [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/sWpw8Nm3On/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-25 01:34:02 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-26 01:33:50 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-26 01:33:50 (7111) [INFO] Newer version of script found. Downloading.
* 2024-04-26 01:33:51 (7120) [INFO] Script update to version 35 successful.
* 2024-04-26 01:33:52 (198) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-26 01:33:52 (2016) [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-04-26 01:33:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-26 01:33:53 (715) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-26 01:33:53 (722) [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.

* 2024-04-26 01:34:05 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-26 01:34:05 (1903) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-26 01:34:05 (1903) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-26 01:34:05 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-26 01:34:05 (1881) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-26 01:34:05 (1903) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-26 01:34:05 (1903) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-26 01:34:05 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-26 01:34:05 (1903) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-26 01:34:10 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-26 01:34:10 (1786) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-26 01:34:10 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-26 01:34:11 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1hBa5jtQD6/ea_profile.json
* 2024-04-26 01:34:15 (345) [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/1hBa5jtQD6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-26 01:34:15 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-27 01:34:47 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-27 01:34:47 (7138) [INFO] Script is up to date.
* 2024-04-27 01:34:48 (198) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-27 01:34:48 (2016) [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-04-27 01:34:48 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-27 01:34:49 (715) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-27 01:34:49 (722) [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.

* 2024-04-27 01:35:13 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-27 01:35:13 (1903) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-27 01:35:13 (1903) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-27 01:35:13 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-27 01:35:13 (1881) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-27 01:35:13 (1903) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-27 01:35:13 (1903) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-27 01:35:13 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-27 01:35:13 (1903) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-27 01:35:16 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-27 01:35:16 (1786) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-27 01:35:17 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-27 01:35:17 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HZcUC5xffT/ea_profile.json
* 2024-04-27 01:35:20 (345) [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/HZcUC5xffT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-27 01:35:20 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-28 01:34:20 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-28 01:34:20 (7138) [INFO] Script is up to date.
* 2024-04-28 01:34:21 (198) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-28 01:34:21 (2016) [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-04-28 01:34:21 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-28 01:34:22 (715) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-28 01:34:22 (722) [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.

* 2024-04-28 01:34:30 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-28 01:34:30 (1903) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-28 01:34:30 (1903) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-28 01:34:30 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-28 01:34:30 (1881) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-28 01:34:30 (1903) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-28 01:34:30 (1903) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-28 01:34:30 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-28 01:34:30 (1903) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-28 01:34:39 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-28 01:34:39 (1786) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 288229.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  34 M RSS (325 MB VSZ)
    Started: Sun Apr 28 01:34:29 2024 - 00:02 ago
    State  : Sleeping, pid: 288229
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Sun Apr 28 01:34:29 2024 - 00:04 ago
    State  : Running, pid: 288229
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-28 01:34:40 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-28 01:34:40 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qcAdQy9PAp/ea_profile.json
* 2024-04-28 01:34:45 (345) [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/qcAdQy9PAp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-28 01:34:45 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-29 01:33:32 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-29 01:33:33 (7138) [INFO] Script is up to date.
* 2024-04-29 01:33:34 (198) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-29 01:33:34 (2016) [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-04-29 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-29 01:33:35 (715) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-29 01:33:35 (722) [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.

* 2024-04-29 01:33:42 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-29 01:33:42 (1903) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-29 01:33:42 (1903) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-29 01:33:42 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-29 01:33:42 (1881) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-29 01:33:42 (1903) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-29 01:33:42 (1903) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-29 01:33:42 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-29 01:33:42 (1903) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-29 01:33:45 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-29 01:33:45 (1786) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-29 01:33:45 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-29 01:33:45 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eQR4wjja_E/ea_profile.json
* 2024-04-29 01:33:48 (345) [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/eQR4wjja_E/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-29 01:33:48 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-30 01:33:41 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-30 01:33:41 (7138) [INFO] Script is up to date.
* 2024-04-30 01:33:42 (198) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-04-30 01:33:42 (2016) [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-04-30 01:33:43 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-04-30 01:33:43 (715) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-04-30 01:33:43 (722) [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.

* 2024-04-30 01:34:55 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-04-30 01:34:55 (1903) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-04-30 01:34:55 (1903) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-04-30 01:34:55 (1881) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-30 01:34:55 (1881) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-04-30 01:34:55 (1903) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-04-30 01:34:55 (1903) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-04-30 01:34:55 (1881) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-04-30 01:34:55 (1903) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-04-30 01:35:04 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-30 01:35:04 (1786) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 122490.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (325 MB VSZ)
    Started: Tue Apr 30 01:34:54 2024 - 00:01 ago
    State  : Sleeping, pid: 122490
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  37 M RSS (331 MB VSZ)
    Started: Tue Apr 30 01:34:54 2024 - 00:03 ago
    State  : Uninterruptible, pid: 122490
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (332 MB VSZ)
    Started: Tue Apr 30 01:34:54 2024 - 00:05 ago
    State  : Uninterruptible, pid: 122490
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-04-30 01:35:04 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-30 01:35:05 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YMCfBdbtFi/ea_profile.json
* 2024-04-30 01:35:10 (345) [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/YMCfBdbtFi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-30 01:35:10 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-01 01:33:35 (7116) [INFO] Self-update of script version 35 requested.
* 2024-05-01 01:33:35 (7121) [INFO] Newer version of script found. Downloading.
* 2024-05-01 01:33:36 (7130) [INFO] Script update to version 36 successful.
* 2024-05-01 01:33:37 (199) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-01 01:33:37 (2017) [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-05-01 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-01 01:33:38 (716) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-01 01:33:38 (723) [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.

* 2024-05-01 01:33:53 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-01 01:33:53 (1904) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-01 01:33:53 (1904) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-01 01:33:53 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-01 01:33:53 (1882) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-01 01:33:53 (1904) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-01 01:33:53 (1904) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-01 01:33:53 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-01 01:33:53 (1904) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-01 01:33:58 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-01 01:33:58 (1787) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-01 01:33:58 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-01 01:33:58 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lFvdKWfv77/ea_profile.json
* 2024-05-01 01:34:01 (346) [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/lFvdKWfv77/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-01 01:34:01 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-02 01:33:59 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-02 01:33:59 (7530) [INFO] Script is up to date.
* 2024-05-02 01:34:01 (199) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-02 01:34:01 (2017) [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-05-02 01:34:01 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-02 01:34:02 (716) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-02 01:34:02 (723) [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.

* 2024-05-02 01:34:13 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-02 01:34:13 (1904) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-02 01:34:13 (1904) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-02 01:34:13 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-02 01:34:13 (1882) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-02 01:34:13 (1904) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-02 01:34:13 (1904) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-02 01:34:13 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-02 01:34:13 (1904) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-02 01:34:16 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-02 01:34:16 (1787) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-02 01:34:16 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-02 01:34:17 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C8CpWq1uCJ/ea_profile.json
* 2024-05-02 01:34:21 (346) [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/C8CpWq1uCJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-02 01:34:21 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-03 01:33:29 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-03 01:33:29 (7530) [INFO] Script is up to date.
* 2024-05-03 01:33:30 (199) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-03 01:33:30 (2017) [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-05-03 01:33:30 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-03 01:33:32 (716) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-03 01:33:32 (723) [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.

* 2024-05-03 01:33:40 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-03 01:33:40 (1904) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-03 01:33:40 (1904) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-03 01:33:40 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-03 01:33:40 (1882) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-03 01:33:40 (1904) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-03 01:33:40 (1904) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-03 01:33:40 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-03 01:33:40 (1904) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-03 01:33:43 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-03 01:33:43 (1787) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-03 01:33:43 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-03 01:33:43 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JZPFvr4qCs/ea_profile.json
* 2024-05-03 01:33:46 (346) [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/JZPFvr4qCs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-03 01:33:46 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-04 01:36:50 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-04 01:36:51 (7530) [INFO] Script is up to date.
* 2024-05-04 01:36:52 (199) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-04 01:36:52 (2017) [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-05-04 01:36:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-04 01:36:54 (716) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-04 01:36:54 (723) [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.

* 2024-05-04 01:37:12 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-04 01:37:12 (1904) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-04 01:37:12 (1904) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-04 01:37:12 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-04 01:37:12 (1882) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-04 01:37:12 (1904) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-04 01:37:12 (1904) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-04 01:37:12 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-04 01:37:12 (1904) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-04 01:37:17 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-04 01:37:17 (1787) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-04 01:37:17 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-04 01:37:17 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IKhKoCEicI/ea_profile.json
* 2024-05-04 01:37:22 (346) [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/IKhKoCEicI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-04 01:37:22 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-05 01:34:48 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-05 01:34:48 (7530) [INFO] Script is up to date.
* 2024-05-05 01:34:50 (199) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-05 01:34:50 (2017) [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-05-05 01:34:50 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-05 01:34:50 (716) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-05 01:34:50 (723) [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.

* 2024-05-05 01:35:01 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-05 01:35:01 (1904) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-05 01:35:01 (1904) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-05 01:35:01 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-05 01:35:01 (1882) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-05 01:35:01 (1904) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-05 01:35:01 (1904) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-05 01:35:01 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-05 01:35:01 (1904) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-05 01:35:08 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-05 01:35:08 (1787) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-05 01:35:08 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-05 01:35:09 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UVPblOYO2q/ea_profile.json
* 2024-05-05 01:35:13 (346) [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/UVPblOYO2q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-05 01:35:13 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-06 01:33:47 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-06 01:33:47 (7530) [INFO] Script is up to date.
* 2024-05-06 01:33:48 (199) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-06 01:33:48 (2017) [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-05-06 01:33:48 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-06 01:33:49 (716) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-06 01:33:49 (723) [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.

* 2024-05-06 01:34:00 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-06 01:34:00 (1904) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-06 01:34:00 (1904) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-06 01:34:00 (1882) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-06 01:34:00 (1882) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-06 01:34:00 (1904) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-06 01:34:00 (1904) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-06 01:34:00 (1882) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-06 01:34:00 (1904) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-06 01:34:04 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-06 01:34:04 (1787) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Peer reports incompatible or unsupported protocol version."
Trying other mirror.


 One of the configured repositories failed (EL-7 - Imunify360),
 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=imunify360 ...

     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 imunify360
        or
            subscription-manager repos --disable=imunify360

     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=imunify360.skip_if_unavailable=true

failure: repodata/repomd.xml from imunify360: [Errno 256] No more mirrors to try.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Peer reports incompatible or unsupported protocol version."
* 2024-05-06 01:34:04 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-06 01:34:04 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XqIAIdpJpQ/ea_profile.json
* 2024-05-06 01:34:08 (346) [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/XqIAIdpJpQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-06 01:34:08 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-07 01:33:43 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-07 01:33:43 (7513) [INFO] Newer version of script found. Downloading.
* 2024-05-07 01:33:43 (7522) [INFO] Script update to version 37 successful.
* 2024-05-07 01:33:45 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-07 01:33:45 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-07 01:33:45 (6322) [INFO] 
* 2024-05-07 01:33:45 (6352) [INFO] 
* 2024-05-07 01:33:45 (2056) [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-05-07 01:33:45 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-07 01:33:46 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-07 01:33:46 (726) [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.

* 2024-05-07 01:33:51 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-07 01:33:51 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-07 01:33:51 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-07 01:33:51 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-07 01:33:51 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-07 01:33:51 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-07 01:33:51 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-07 01:33:51 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-07 01:33:51 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-07 01:33:55 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-07 01:33:55 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-07 01:33:55 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-07 01:33:55 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eTgc2Pg_A3/ea_profile.json
* 2024-05-07 01:33:59 (349) [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/eTgc2Pg_A3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-07 01:33:59 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-08 01:33:31 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-08 01:33:31 (7570) [INFO] Script is up to date.
* 2024-05-08 01:33:32 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-08 01:33:32 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-08 01:33:32 (6322) [INFO] 
* 2024-05-08 01:33:32 (6352) [INFO] 
* 2024-05-08 01:33:32 (2056) [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-05-08 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-08 01:33:32 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-08 01:33:32 (726) [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.

* 2024-05-08 01:33:46 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-08 01:33:46 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-08 01:33:46 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-08 01:33:46 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-08 01:33:46 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-08 01:33:46 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-08 01:33:46 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-08 01:33:46 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-08 01:33:46 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-08 01:33:49 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-08 01:33:49 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-08 01:33:49 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-08 01:33:49 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NaGo_SKEp3/ea_profile.json
* 2024-05-08 01:33:51 (349) [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/NaGo_SKEp3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-08 01:33:51 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-09 01:33:54 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-09 01:33:54 (7570) [INFO] Script is up to date.
* 2024-05-09 01:33:55 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-09 01:33:55 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-09 01:33:55 (6322) [INFO] 
* 2024-05-09 01:33:55 (6352) [INFO] 
* 2024-05-09 01:33:55 (2056) [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-05-09 01:33:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-09 01:33:56 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-09 01:33:56 (726) [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.

* 2024-05-09 01:34:04 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-09 01:34:04 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-09 01:34:04 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-09 01:34:04 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-09 01:34:04 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-09 01:34:04 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-09 01:34:04 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-09 01:34:04 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-09 01:34:04 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-09 01:34:09 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-09 01:34:09 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-09 01:34:09 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-09 01:34:09 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/heK9KVm4qA/ea_profile.json
* 2024-05-09 01:34:13 (349) [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/heK9KVm4qA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-09 01:34:13 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-10 01:33:51 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-10 01:33:51 (7570) [INFO] Script is up to date.
* 2024-05-10 01:33:52 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-10 01:33:52 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-10 01:33:52 (6322) [INFO] 
* 2024-05-10 01:33:52 (6352) [INFO] 
* 2024-05-10 01:33:52 (2056) [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-05-10 01:33:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-10 01:33:53 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-10 01:33:53 (726) [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.

* 2024-05-10 01:34:03 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-10 01:34:03 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-10 01:34:03 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-10 01:34:03 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-10 01:34:03 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-10 01:34:03 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-10 01:34:03 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-10 01:34:03 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-10 01:34:03 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-10 01:34:12 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-10 01:34:12 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-10 01:34:12 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-10 01:34:12 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LqG3Y3I4Cu/ea_profile.json
* 2024-05-10 01:34:17 (349) [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/LqG3Y3I4Cu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-10 01:34:17 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-11 01:35:04 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-11 01:35:04 (7570) [INFO] Script is up to date.
* 2024-05-11 01:35:05 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-11 01:35:05 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-11 01:35:05 (6322) [INFO] 
* 2024-05-11 01:35:05 (6352) [INFO] 
* 2024-05-11 01:35:05 (2056) [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-05-11 01:35:05 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-11 01:35:07 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-11 01:35:07 (726) [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.

* 2024-05-11 01:35:22 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-11 01:35:22 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-11 01:35:22 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-11 01:35:22 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-11 01:35:22 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-11 01:35:22 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-11 01:35:22 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-11 01:35:22 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-11 01:35:22 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-11 01:35:24 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-11 01:35:24 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-11 01:35:24 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-11 01:35:24 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZahxmSrm8i/ea_profile.json
* 2024-05-11 01:35:28 (349) [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/ZahxmSrm8i/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-11 01:35:28 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-12 01:34:27 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-12 01:34:27 (7570) [INFO] Script is up to date.
* 2024-05-12 01:34:28 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-12 01:34:28 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-12 01:34:28 (6322) [INFO] 
* 2024-05-12 01:34:28 (6352) [INFO] 
* 2024-05-12 01:34:28 (2056) [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-05-12 01:34:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-12 01:34:29 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-12 01:34:29 (726) [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.

* 2024-05-12 01:34:35 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-12 01:34:35 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-12 01:34:35 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-12 01:34:35 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-12 01:34:35 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-12 01:34:35 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-12 01:34:35 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-12 01:34:35 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-12 01:34:35 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-12 01:34:37 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-12 01:34:37 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-12 01:34:37 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-12 01:34:37 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KktPTdfkZa/ea_profile.json
* 2024-05-12 01:34:40 (349) [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/KktPTdfkZa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-12 01:34:40 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-13 01:33:44 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-13 01:33:44 (7570) [INFO] Script is up to date.
* 2024-05-13 01:33:45 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-13 01:33:46 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-13 01:33:46 (6322) [INFO] 
* 2024-05-13 01:33:46 (6352) [INFO] 
* 2024-05-13 01:33:46 (2056) [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-05-13 01:33:46 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-13 01:33:47 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-13 01:33:47 (726) [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.

* 2024-05-13 01:33:58 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-13 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-13 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-13 01:33:58 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-13 01:33:58 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-13 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-13 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-13 01:33:58 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-13 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-13 01:34:01 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-13 01:34:01 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-13 01:34:01 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-13 01:34:01 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BEVO0XhqhR/ea_profile.json
* 2024-05-13 01:34:06 (349) [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/BEVO0XhqhR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-13 01:34:06 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-14 01:33:53 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-14 01:33:53 (7570) [INFO] Script is up to date.
* 2024-05-14 01:33:53 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-14 01:33:54 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-14 01:33:54 (6322) [INFO] 
* 2024-05-14 01:33:54 (6352) [INFO] 
* 2024-05-14 01:33:54 (2056) [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-05-14 01:33:54 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-14 01:33:54 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-14 01:33:54 (726) [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.

* 2024-05-14 01:34:11 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-14 01:34:11 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-14 01:34:11 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-14 01:34:11 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-14 01:34:11 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-14 01:34:11 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-14 01:34:11 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-14 01:34:11 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-14 01:34:11 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-14 01:34:15 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-14 01:34:15 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-14 01:34:15 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-14 01:34:15 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CwR5jbqp5j/ea_profile.json
* 2024-05-14 01:34:19 (349) [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/CwR5jbqp5j/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-14 01:34:19 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-15 01:33:52 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-15 01:33:52 (7570) [INFO] Script is up to date.
* 2024-05-15 01:33:53 (200) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-15 01:33:54 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-15 01:33:54 (6322) [INFO] 
* 2024-05-15 01:33:54 (6352) [INFO] 
* 2024-05-15 01:33:54 (2056) [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-05-15 01:33:54 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-15 01:33:54 (719) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-15 01:33:54 (726) [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.

* 2024-05-15 01:33:58 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-15 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-15 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-15 01:33:58 (1921) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-15 01:33:58 (1921) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-15 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-15 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-15 01:33:58 (1921) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-15 01:33:58 (1943) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-15 01:34:03 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-15 01:34:03 (1826) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-15 01:34:03 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-15 01:34:03 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jUYln_ugG3/ea_profile.json
* 2024-05-15 01:34:08 (349) [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/jUYln_ugG3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-15 01:34:08 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-16 01:33:40 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-16 01:33:40 (7553) [INFO] Newer version of script found. Downloading.
* 2024-05-16 01:33:40 (7562) [INFO] Script update to version 38 successful.
* 2024-05-16 01:33:41 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-16 01:33:42 (2163) [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-05-16 01:33:42 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-16 01:33:42 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-16 01:33:42 (727) [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.

* 2024-05-16 01:33:52 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-16 01:33:52 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-16 01:33:52 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-16 01:33:52 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-16 01:33:52 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-16 01:33:52 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-16 01:33:52 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-16 01:33:52 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-16 01:33:52 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-16 01:33:56 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-16 01:33:56 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-16 01:33:57 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-16 01:33:57 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/00nsoZtGPt/ea_profile.json
* 2024-05-16 01:34:04 (350) [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/00nsoZtGPt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-16 01:34:04 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-17 01:33:50 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-17 01:33:50 (7748) [INFO] Script is up to date.
* 2024-05-17 01:33:51 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-17 01:33:51 (2163) [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-05-17 01:33:51 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-17 01:33:52 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-17 01:33:52 (727) [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.

* 2024-05-17 01:33:56 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-17 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-17 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-17 01:33:56 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-17 01:33:56 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-17 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-17 01:33:57 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-17 01:33:57 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-17 01:33:57 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-17 01:34:02 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-17 01:34:02 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-17 01:34:02 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-17 01:34:02 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2oh3Z55D3h/ea_profile.json
* 2024-05-17 01:34:06 (350) [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/2oh3Z55D3h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-17 01:34:06 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-18 01:35:22 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-18 01:35:22 (7748) [INFO] Script is up to date.
* 2024-05-18 01:35:23 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-18 01:35:23 (2163) [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-05-18 01:35:23 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-18 01:35:24 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-18 01:35:24 (727) [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.

* 2024-05-18 01:35:41 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-18 01:35:41 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-18 01:35:41 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-18 01:35:41 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-18 01:35:41 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-18 01:35:41 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-18 01:35:41 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-18 01:35:41 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-18 01:35:41 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-18 01:35:51 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-18 01:35:51 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-18 01:35:51 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-18 01:35:51 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oFYAxQt6ck/ea_profile.json
* 2024-05-18 01:36:04 (350) [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/oFYAxQt6ck/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-18 01:36:04 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-19 01:35:03 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-19 01:35:03 (7748) [INFO] Script is up to date.
* 2024-05-19 01:35:04 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-19 01:35:04 (2163) [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-05-19 01:35:04 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-19 01:35:06 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-19 01:35:06 (727) [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.

* 2024-05-19 01:35:10 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-19 01:35:10 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-19 01:35:10 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-19 01:35:10 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-19 01:35:10 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-19 01:35:10 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-19 01:35:10 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-19 01:35:10 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-19 01:35:10 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-19 01:35:16 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-19 01:35:16 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-19 01:35:16 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-19 01:35:16 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N07IwmANLi/ea_profile.json
* 2024-05-19 01:35:22 (350) [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/N07IwmANLi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-19 01:35:22 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-20 01:33:39 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-20 01:33:39 (7748) [INFO] Script is up to date.
* 2024-05-20 01:33:40 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-20 01:33:40 (2163) [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-05-20 01:33:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-20 01:33:40 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-20 01:33:40 (727) [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.

* 2024-05-20 01:33:56 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-20 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-20 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-20 01:33:56 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-20 01:33:56 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-20 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-20 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-20 01:33:56 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-20 01:33:56 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-20 01:34:00 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-20 01:34:00 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-20 01:34:00 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-20 01:34:00 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Z2LtJH1oVc/ea_profile.json
* 2024-05-20 01:34:10 (350) [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/Z2LtJH1oVc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-20 01:34:10 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-21 01:34:45 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-21 01:34:45 (7748) [INFO] Script is up to date.
* 2024-05-21 01:34:45 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-21 01:34:46 (2163) [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-05-21 01:34:46 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-21 01:34:46 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-21 01:34:46 (727) [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.

* 2024-05-21 01:34:53 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-21 01:34:53 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-21 01:34:53 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-21 01:34:53 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-21 01:34:53 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-21 01:34:53 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-21 01:34:53 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-21 01:34:53 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-21 01:34:53 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-21 01:34:59 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-21 01:34:59 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-21 01:34:59 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-21 01:34:59 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZKyUPgRTDe/ea_profile.json
* 2024-05-21 01:35:08 (350) [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/ZKyUPgRTDe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-21 01:35:08 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-22 01:33:58 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-22 01:33:58 (7748) [INFO] Script is up to date.
* 2024-05-22 01:33:59 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-22 01:33:59 (2163) [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-05-22 01:33:59 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-22 01:34:00 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-22 01:34:00 (727) [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.

* 2024-05-22 01:34:24 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-22 01:34:24 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-22 01:34:24 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-22 01:34:24 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-22 01:34:24 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-22 01:34:24 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-22 01:34:24 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-22 01:34:24 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-22 01:34:24 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-22 01:34:28 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-22 01:34:28 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-22 01:34:28 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-22 01:34:28 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GgTcnQaigz/ea_profile.json
* 2024-05-22 01:34:33 (350) [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/GgTcnQaigz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-22 01:34:33 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-23 01:33:38 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-23 01:33:38 (7748) [INFO] Script is up to date.
* 2024-05-23 01:33:39 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-23 01:33:39 (2163) [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-05-23 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-23 01:33:40 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-23 01:33:40 (727) [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.

* 2024-05-23 01:33:43 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-23 01:33:43 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-23 01:33:43 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-23 01:33:43 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-23 01:33:43 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-23 01:33:43 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-23 01:33:43 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-23 01:33:43 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-23 01:33:43 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-23 01:33:47 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-23 01:33:47 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-23 01:33:47 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-23 01:33:47 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y_kb1SEwMS/ea_profile.json
* 2024-05-23 01:33:50 (350) [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/Y_kb1SEwMS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-23 01:33:50 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-24 01:33:27 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-24 01:33:27 (7748) [INFO] Script is up to date.
* 2024-05-24 01:33:28 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-24 01:33:28 (2163) [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-05-24 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-24 01:33:29 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-24 01:33:29 (727) [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.

* 2024-05-24 01:33:44 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-24 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-24 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-24 01:33:44 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-24 01:33:44 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-24 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-24 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-24 01:33:44 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-24 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-24 01:33:48 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-24 01:33:48 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-24 01:33:48 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-24 01:33:48 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9ttUGrE54v/ea_profile.json
* 2024-05-24 01:33:51 (350) [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/9ttUGrE54v/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-24 01:33:51 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-25 01:34:16 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-25 01:34:16 (7748) [INFO] Script is up to date.
* 2024-05-25 01:34:17 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-25 01:34:17 (2163) [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-05-25 01:34:17 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-25 01:34:17 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-25 01:34:17 (727) [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.

* 2024-05-25 01:34:28 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-25 01:34:28 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-25 01:34:28 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-25 01:34:28 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-25 01:34:28 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-25 01:34:28 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-25 01:34:28 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-25 01:34:28 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-25 01:34:28 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-25 01:34:33 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-25 01:34:33 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-25 01:34:33 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-25 01:34:33 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cZ4qwpM9kd/ea_profile.json
* 2024-05-25 01:34:38 (350) [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/cZ4qwpM9kd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-25 01:34:38 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-26 01:33:55 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-26 01:33:55 (7748) [INFO] Script is up to date.
* 2024-05-26 01:33:56 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-26 01:33:56 (2163) [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-05-26 01:33:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-26 01:33:56 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-26 01:33:56 (727) [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.

* 2024-05-26 01:34:07 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-26 01:34:07 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-26 01:34:07 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-26 01:34:07 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-26 01:34:07 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-26 01:34:07 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-26 01:34:07 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-26 01:34:07 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-26 01:34:07 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-26 01:34:11 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-26 01:34:11 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-26 01:34:12 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-26 01:34:12 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4uwdQRhW0S/ea_profile.json
* 2024-05-26 01:34:16 (350) [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/4uwdQRhW0S/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-26 01:34:16 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-28 01:33:29 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-28 01:33:29 (7748) [INFO] Script is up to date.
* 2024-05-28 01:33:30 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-28 01:33:30 (2163) [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-05-28 01:33:30 (201) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-05-28 01:33:30 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-28 01:33:30 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-28 01:33:30 (727) [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.

* 2024-05-28 01:33:44 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-28 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-28 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-28 01:33:44 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-28 01:33:44 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-28 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-28 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-28 01:33:44 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-28 01:33:44 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-28 01:33:49 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-28 01:33:49 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-28 01:33:49 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-28 01:33:49 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OalExaZpjC/ea_profile.json
* 2024-05-28 01:33:54 (350) [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/OalExaZpjC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-28 01:33:54 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-29 01:33:35 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-29 01:33:36 (7748) [INFO] Script is up to date.
* 2024-05-29 01:33:36 (201) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-29 01:33:36 (2163) [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-05-29 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-29 01:33:37 (720) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-29 01:33:37 (727) [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.

* 2024-05-29 01:33:50 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-29 01:33:50 (2050) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-29 01:33:50 (2050) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-29 01:33:50 (2028) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-29 01:33:50 (2028) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-29 01:33:50 (2050) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-29 01:33:50 (2050) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-29 01:33:50 (2028) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-29 01:33:50 (2050) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-29 01:33:54 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-29 01:33:54 (1933) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-29 01:33:54 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-29 01:33:54 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vwtpkrYsxc/ea_profile.json
* 2024-05-29 01:33:59 (350) [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/vwtpkrYsxc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-29 01:33:59 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-30 01:34:00 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-30 01:34:00 (7731) [INFO] Newer version of script found. Downloading.
* 2024-05-30 01:34:01 (7740) [INFO] Script update to version 39 successful.
* 2024-05-30 01:34:02 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-30 01:34:02 (2212) [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-05-30 01:34:02 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-30 01:34:02 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-05-30 01:34:02 (6568) [INFO] 
* 2024-05-30 01:34:07 (6581) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-05-30 01:34:07 (6598) [INFO] 
* 2024-05-30 01:34:07 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-30 01:34:07 (730) [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.

* 2024-05-30 01:34:13 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-30 01:34:13 (2099) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-30 01:34:13 (2099) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-30 01:34:13 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-30 01:34:13 (2077) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-30 01:34:13 (2099) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-30 01:34:13 (2099) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-30 01:34:13 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-30 01:34:13 (2099) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-30 01:34:18 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-30 01:34:18 (1982) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-30 01:34:18 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-30 01:34:18 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w58fHnO_xe/ea_profile.json
* 2024-05-30 01:34:24 (353) [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/w58fHnO_xe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-05-30 01:34:24 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-31 01:33:30 (7795) [INFO] Self-update of script version 39 requested.
* 2024-05-31 01:33:30 (7817) [INFO] Script is up to date.
* 2024-05-31 01:33:31 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-05-31 01:33:31 (2212) [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-05-31 01:33:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-05-31 01:33:31 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-05-31 01:33:31 (6568) [INFO] 
* 2024-05-31 01:33:37 (6581) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-05-31 01:33:37 (6598) [INFO] 
* 2024-05-31 01:33:38 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-05-31 01:33:38 (730) [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.

* 2024-05-31 01:33:49 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-05-31 01:33:49 (2099) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-05-31 01:33:49 (2099) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-05-31 01:33:49 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-31 01:33:49 (2077) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-05-31 01:33:49 (2099) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-05-31 01:33:49 (2099) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-05-31 01:33:49 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-05-31 01:33:49 (2099) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-05-31 01:33:53 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-31 01:33:53 (1982) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-05-31 01:33:53 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-31 01:33:53 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5sOb0edDWs/ea_profile.json
* 2024-05-31 01:33:58 (353) [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/5sOb0edDWs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-05-31 01:33:58 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-01 01:34:50 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-01 01:34:50 (7817) [INFO] Script is up to date.
* 2024-06-01 01:34:51 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-01 01:34:51 (2212) [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-06-01 01:34:51 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-01 01:34:51 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-01 01:34:51 (6568) [INFO] 
* 2024-06-01 01:34:57 (6581) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-01 01:34:57 (6598) [INFO] 
* 2024-06-01 01:34:58 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-01 01:34:58 (730) [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.

* 2024-06-01 01:35:04 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-01 01:35:04 (2099) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-01 01:35:04 (2099) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-01 01:35:04 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-01 01:35:04 (2077) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-01 01:35:04 (2099) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-01 01:35:04 (2099) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-01 01:35:04 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-01 01:35:04 (2099) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-01 01:35:10 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-01 01:35:10 (1982) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-01 01:35:10 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-01 01:35:10 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vXhwvhG7ct/ea_profile.json
* 2024-06-01 01:35:15 (353) [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/vXhwvhG7ct/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-01 01:35:15 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-02 01:34:42 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-02 01:34:42 (7817) [INFO] Script is up to date.
* 2024-06-02 01:34:43 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-02 01:34:43 (2212) [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-06-02 01:34:43 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-02 01:34:43 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-02 01:34:43 (6568) [INFO] 
* 2024-06-02 01:34:47 (6581) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-02 01:34:48 (6598) [INFO] 
* 2024-06-02 01:34:48 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-02 01:34:48 (730) [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.

* 2024-06-02 01:34:57 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-02 01:34:57 (2099) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-02 01:34:57 (2099) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-02 01:34:57 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-02 01:34:57 (2077) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-02 01:34:57 (2099) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-02 01:34:57 (2099) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-02 01:34:57 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-02 01:34:57 (2099) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-02 01:35:01 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-02 01:35:01 (1982) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-02 01:35:01 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-02 01:35:01 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wKbM7q0ZGE/ea_profile.json
* 2024-06-02 01:35:08 (353) [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/wKbM7q0ZGE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-02 01:35:08 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-03 01:33:38 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-03 01:33:38 (7817) [INFO] Script is up to date.
* 2024-06-03 01:33:39 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-03 01:33:39 (2212) [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-06-03 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-03 01:33:39 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-03 01:33:39 (6568) [INFO] 
* 2024-06-03 01:33:43 (6581) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-03 01:33:43 (6598) [INFO] 
* 2024-06-03 01:33:43 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-03 01:33:43 (730) [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.

* 2024-06-03 01:33:48 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-03 01:33:48 (2099) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-03 01:33:48 (2099) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-03 01:33:48 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-03 01:33:48 (2077) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-03 01:33:48 (2099) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-03 01:33:48 (2099) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-03 01:33:48 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-03 01:33:48 (2099) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-03 01:33:53 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-03 01:33:53 (1982) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-03 01:33:53 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-03 01:33:53 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HhZp9C5egy/ea_profile.json
* 2024-06-03 01:33:58 (353) [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/HhZp9C5egy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-03 01:33:58 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-04 01:33:35 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-04 01:33:35 (7817) [INFO] Script is up to date.
* 2024-06-04 01:33:36 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-04 01:33:36 (2212) [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-06-04 01:33:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-04 01:33:36 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-04 01:33:36 (6568) [INFO] 
* 2024-06-04 01:33:41 (6581) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-04 01:33:41 (6598) [INFO] 
* 2024-06-04 01:33:42 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-04 01:33:42 (730) [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.

* 2024-06-04 01:33:53 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-04 01:33:53 (2099) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-04 01:33:53 (2099) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-04 01:33:53 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-04 01:33:53 (2077) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-04 01:33:53 (2099) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-04 01:33:53 (2099) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-04 01:33:53 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-04 01:33:53 (2099) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-04 01:33:58 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-04 01:33:58 (1982) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-04 01:33:58 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-04 01:33:58 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ab_smzairX/ea_profile.json
* 2024-06-04 01:34:04 (353) [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/ab_smzairX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-04 01:34:04 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-05 01:33:39 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-05 01:33:39 (7817) [INFO] Script is up to date.
* 2024-06-05 01:33:40 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-05 01:33:40 (2212) [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-06-05 01:33:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-05 01:33:40 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-05 01:33:40 (6568) [INFO] 
* 2024-06-05 01:33:45 (6581) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-05 01:33:45 (6598) [INFO] 
* 2024-06-05 01:33:46 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-05 01:33:46 (730) [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.

* 2024-06-05 01:33:47 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-05 01:33:47 (2099) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-05 01:33:47 (2099) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-05 01:33:47 (2077) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-05 01:33:47 (2077) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-05 01:33:47 (2099) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-05 01:33:47 (2099) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-05 01:33:47 (2077) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-05 01:33:47 (2099) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-05 01:33:51 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-05 01:33:51 (1982) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-05 01:33:51 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-05 01:33:51 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZkARftn_b0/ea_profile.json
* 2024-06-05 01:33:57 (353) [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/ZkARftn_b0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-05 01:33:57 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-06 01:33:50 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-06 01:33:50 (7800) [INFO] Newer version of script found. Downloading.
* 2024-06-06 01:33:51 (7809) [INFO] Script update to version 40 successful.
* 2024-06-06 01:33:52 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-06 01:33:52 (2224) [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-06-06 01:33:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-06 01:33:52 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-06 01:33:52 (6580) [INFO] 
* 2024-06-06 01:33:57 (6593) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-06 01:33:57 (6610) [INFO] 
* 2024-06-06 01:33:58 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-06 01:33:58 (730) [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.

* 2024-06-06 01:34:18 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-06 01:34:18 (2111) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-06 01:34:18 (2111) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-06 01:34:18 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-06 01:34:18 (2089) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-06 01:34:18 (2111) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-06 01:34:18 (2111) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-06 01:34:18 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-06 01:34:18 (2111) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-06 01:34:53 (1982) [WARN] Initial run of "yum makecache" failed: http://mirror.vcu.edu/pub/gnu_linux/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.vcu.edu/pub/gnu_linux/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-06 01:34:53 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-06 01:34:53 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-06 01:34:53 (6580) [INFO] 
* 2024-06-06 01:34:54 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-06 01:34:54 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-06 01:34:54 (6593) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-06 01:34:54 (6593) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-06 01:34:54 (6593) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-06 01:34:54 (6593) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-06 01:34:54 (6593) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-06 01:34:54 (6593) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-06 01:34:54 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-06 01:34:54 (6593) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-06 01:34:54 (6610) [INFO] 
* 2024-06-06 01:35:03 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-06 01:35:03 (1993) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-06 01:35:04 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-06 01:35:04 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6QpfbkrCK_/ea_profile.json
* 2024-06-06 01:35:10 (353) [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/6QpfbkrCK_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-06 01:35:10 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-07 01:34:59 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-07 01:35:00 (7829) [INFO] Script is up to date.
* 2024-06-07 01:35:00 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-07 01:35:01 (2224) [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-06-07 01:35:01 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-07 01:35:01 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-07 01:35:01 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-07 01:35:01 (6580) [INFO] 
* 2024-06-07 01:39:22 (6593) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-07 01:39:22 (6610) [INFO] 
* 2024-06-07 01:39:23 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-07 01:39:23 (730) [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.

* 2024-06-07 01:39:24 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-07 01:39:24 (2111) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-07 01:39:24 (2111) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-07 01:39:24 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-07 01:39:24 (2089) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-07 01:39:24 (2111) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-07 01:39:24 (2111) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-07 01:39:24 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-07 01:39:24 (2111) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-07 01:39:28 (1982) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-07 01:39:28 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-07 01:39:28 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-07 01:39:28 (6580) [INFO] 
* 2024-06-07 01:39:28 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-07 01:39:28 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-07 01:39:28 (6593) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-07 01:39:28 (6593) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-07 01:39:28 (6593) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-07 01:39:28 (6593) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-07 01:39:28 (6593) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-07 01:39:28 (6593) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-07 01:39:28 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-07 01:39:28 (6593) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-07 01:39:28 (6610) [INFO] 
* 2024-06-07 01:39:35 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-07 01:39:35 (1993) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-07 01:39:35 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-07 01:39:35 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/t1rtzotQfG/ea_profile.json
* 2024-06-07 01:39:54 (353) [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/t1rtzotQfG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-07 01:39:54 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-08 01:35:44 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-08 01:35:44 (7829) [INFO] Script is up to date.
* 2024-06-08 01:35:46 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-08 01:35:46 (2224) [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-06-08 01:35:46 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-08 01:35:46 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-08 01:35:46 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-08 01:35:46 (6580) [INFO] 
* 2024-06-08 01:35:52 (6593) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-08 01:35:52 (6610) [INFO] 
* 2024-06-08 01:35:53 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-08 01:35:53 (730) [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.

* 2024-06-08 01:36:20 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-08 01:36:20 (2111) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-08 01:36:20 (2111) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-08 01:36:20 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-08 01:36:20 (2089) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-08 01:36:20 (2111) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-08 01:36:20 (2111) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-08 01:36:20 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-08 01:36:20 (2111) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-08 01:36:32 (1982) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-08 01:36:32 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-08 01:36:32 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-08 01:36:32 (6580) [INFO] 
* 2024-06-08 01:36:32 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-08 01:36:32 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-08 01:36:32 (6593) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-08 01:36:32 (6593) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-08 01:36:32 (6593) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-08 01:36:32 (6593) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-08 01:36:32 (6593) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-08 01:36:32 (6593) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-08 01:36:32 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-08 01:36:32 (6593) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-08 01:36:32 (6610) [INFO] 
* 2024-06-08 01:36:51 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-08 01:36:51 (1993) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-08 01:36:51 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-08 01:36:51 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JaBfaXQww4/ea_profile.json
* 2024-06-08 01:37:05 (353) [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/JaBfaXQww4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-08 01:37:05 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-09 01:34:51 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-09 01:34:51 (7829) [INFO] Script is up to date.
* 2024-06-09 01:34:52 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-09 01:34:52 (2224) [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-06-09 01:34:52 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-09 01:34:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-09 01:34:52 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-09 01:34:52 (6580) [INFO] 
* 2024-06-09 01:34:59 (6593) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-09 01:34:59 (6610) [INFO] 
* 2024-06-09 01:34:59 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-09 01:34:59 (730) [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.

* 2024-06-09 01:35:14 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-09 01:35:14 (2111) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-09 01:35:14 (2111) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-09 01:35:14 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-09 01:35:14 (2089) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-09 01:35:14 (2111) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-09 01:35:14 (2111) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-09 01:35:14 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-09 01:35:14 (2111) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-09 01:35:17 (1982) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-09 01:35:17 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-09 01:35:17 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-09 01:35:17 (6580) [INFO] 
* 2024-06-09 01:35:17 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-09 01:35:18 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-09 01:35:18 (6593) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-09 01:35:18 (6593) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-09 01:35:18 (6593) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-09 01:35:18 (6593) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-09 01:35:18 (6593) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-09 01:35:18 (6593) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-09 01:35:18 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-09 01:35:18 (6593) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-09 01:35:18 (6610) [INFO] 
* 2024-06-09 01:35:23 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-09 01:35:23 (1993) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-09 01:35:24 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-09 01:35:24 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hmz4fjnJc4/ea_profile.json
* 2024-06-09 01:35:27 (353) [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/hmz4fjnJc4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-09 01:35:27 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-10 01:33:45 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-10 01:33:45 (7829) [INFO] Script is up to date.
* 2024-06-10 01:33:46 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-10 01:33:46 (2224) [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-06-10 01:33:46 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-10 01:33:47 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-10 01:33:47 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-10 01:33:47 (6580) [INFO] 
* 2024-06-10 01:33:51 (6593) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-10 01:33:51 (6610) [INFO] 
* 2024-06-10 01:33:51 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-10 01:33:51 (730) [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.

* 2024-06-10 01:34:08 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-10 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-10 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-10 01:34:08 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-10 01:34:08 (2089) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-10 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-10 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-10 01:34:08 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-10 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-10 01:34:14 (1982) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-10 01:34:14 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-10 01:34:14 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-10 01:34:14 (6580) [INFO] 
* 2024-06-10 01:34:14 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-10 01:34:14 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-10 01:34:14 (6593) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-10 01:34:14 (6593) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-10 01:34:14 (6593) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-10 01:34:14 (6593) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-10 01:34:14 (6593) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-10 01:34:14 (6593) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-10 01:34:14 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-10 01:34:14 (6593) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-10 01:34:14 (6610) [INFO] 
* 2024-06-10 01:34:22 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-10 01:34:22 (1993) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-10 01:34:22 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-10 01:34:22 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lj72knoUwx/ea_profile.json
* 2024-06-10 01:34:28 (353) [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/lj72knoUwx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-10 01:34:28 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-11 01:33:45 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-11 01:33:45 (7829) [INFO] Script is up to date.
* 2024-06-11 01:33:46 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-11 01:33:46 (2224) [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-06-11 01:33:46 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-11 01:33:47 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-11 01:33:47 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-11 01:33:47 (6580) [INFO] 
* 2024-06-11 01:33:52 (6593) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-11 01:33:52 (6610) [INFO] 
* 2024-06-11 01:33:53 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-11 01:33:53 (730) [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.

* 2024-06-11 01:34:08 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-11 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-11 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-11 01:34:08 (2089) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-11 01:34:08 (2089) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-11 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-11 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-11 01:34:08 (2089) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-11 01:34:08 (2111) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-11 01:34:11 (1982) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-11 01:34:11 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-11 01:34:11 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-11 01:34:11 (6580) [INFO] 
* 2024-06-11 01:34:11 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-11 01:34:11 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-11 01:34:11 (6593) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-11 01:34:11 (6593) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-11 01:34:11 (6593) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-11 01:34:11 (6593) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-11 01:34:11 (6593) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-11 01:34:11 (6593) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-11 01:34:11 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-11 01:34:11 (6593) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-11 01:34:11 (6610) [INFO] 
* 2024-06-11 01:34:18 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-11 01:34:18 (1993) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-11 01:34:18 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-11 01:34:18 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/G6yfaoO0I2/ea_profile.json
* 2024-06-11 01:34:22 (353) [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/G6yfaoO0I2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-11 01:34:22 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-14 01:35:39 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-14 01:35:39 (7812) [INFO] Newer version of script found. Downloading.
* 2024-06-14 01:35:39 (7821) [INFO] Script update to version 41 successful.
* 2024-06-14 01:35:40 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-14 01:35:40 (2235) [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-06-14 01:35:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-14 01:35:40 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-14 01:35:40 (6591) [INFO] 
* 2024-06-14 01:35:44 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-14 01:35:44 (6621) [INFO] 
* 2024-06-14 01:35:45 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-14 01:35:45 (730) [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.

* 2024-06-14 01:36:00 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-14 01:36:00 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-14 01:36:00 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-14 01:36:00 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-14 01:36:00 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-14 01:36:00 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-14 01:36:00 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-14 01:36:00 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-14 01:36:00 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-14 01:36:03 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-14 01:36:03 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-14 01:36:03 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-14 01:36:03 (6591) [INFO] 
* 2024-06-14 01:36:03 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-14 01:36:04 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-14 01:36:04 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-14 01:36:04 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-14 01:36:04 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-14 01:36:04 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-14 01:36:04 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-14 01:36:04 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-14 01:36:04 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-14 01:36:04 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-14 01:36:04 (6621) [INFO] 
* 2024-06-14 01:36:10 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-14 01:36:10 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-14 01:36:10 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-14 01:36:10 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ILu1K9FTD9/ea_profile.json
* 2024-06-14 01:36:15 (353) [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/ILu1K9FTD9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-14 01:36:15 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-15 01:34:55 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-15 01:34:55 (7840) [INFO] Script is up to date.
* 2024-06-15 01:34:56 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-15 01:34:56 (2235) [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-06-15 01:34:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-15 01:34:56 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-15 01:34:56 (6591) [INFO] 
* 2024-06-15 01:35:02 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-15 01:35:02 (6621) [INFO] 
* 2024-06-15 01:35:03 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-15 01:35:03 (730) [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.

* 2024-06-15 01:35:09 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-15 01:35:09 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-15 01:35:09 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-15 01:35:09 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-15 01:35:09 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-15 01:35:09 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-15 01:35:09 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-15 01:35:09 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-15 01:35:09 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-15 01:35:12 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-15 01:35:12 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-15 01:35:12 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-15 01:35:12 (6591) [INFO] 
* 2024-06-15 01:35:12 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-15 01:35:12 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-15 01:35:12 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-15 01:35:12 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-15 01:35:12 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-15 01:35:12 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-15 01:35:12 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-15 01:35:12 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-15 01:35:12 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-15 01:35:12 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-15 01:35:12 (6621) [INFO] 
* 2024-06-15 01:35:18 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-15 01:35:18 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-15 01:35:18 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-15 01:35:18 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kcxfZUEVGf/ea_profile.json
* 2024-06-15 01:35:22 (353) [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/kcxfZUEVGf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-15 01:35:22 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-16 01:34:58 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-16 01:34:59 (7840) [INFO] Script is up to date.
* 2024-06-16 01:34:59 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-16 01:35:00 (2235) [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-06-16 01:35:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-16 01:35:00 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-16 01:35:00 (6591) [INFO] 
* 2024-06-16 01:35:06 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-16 01:35:06 (6621) [INFO] 
* 2024-06-16 01:35:07 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-16 01:35:07 (730) [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.

* 2024-06-16 01:35:10 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-16 01:35:10 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-16 01:35:10 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-16 01:35:10 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-16 01:35:10 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-16 01:35:10 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-16 01:35:10 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-16 01:35:10 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-16 01:35:10 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-16 01:35:16 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-16 01:35:16 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-16 01:35:16 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-16 01:35:16 (6591) [INFO] 
* 2024-06-16 01:35:16 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-16 01:35:16 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-16 01:35:16 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-16 01:35:16 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-16 01:35:16 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-16 01:35:16 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-16 01:35:16 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-16 01:35:16 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-16 01:35:16 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-16 01:35:16 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-16 01:35:16 (6621) [INFO] 
* 2024-06-16 01:35:28 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-16 01:35:28 (1996) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 857897.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  34 M RSS (325 MB VSZ)
    Started: Sun Jun 16 01:35:08 2024 - 00:08 ago
    State  : Sleeping, pid: 857897
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  37 M RSS (2.8 GB VSZ)
    Started: Sun Jun 16 01:35:08 2024 - 00:10 ago
    State  : Sleeping, pid: 857897
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  37 M RSS (2.7 GB VSZ)
    Started: Sun Jun 16 01:35:08 2024 - 00:12 ago
    State  : Sleeping, pid: 857897
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Sun Jun 16 01:35:08 2024 - 00:14 ago
    State  : Running, pid: 857897
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-16 01:35:28 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-16 01:35:28 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1rM2datFPJ/ea_profile.json
* 2024-06-16 01:35:32 (353) [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/1rM2datFPJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-16 01:35:32 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-17 01:33:44 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-17 01:33:44 (7840) [INFO] Script is up to date.
* 2024-06-17 01:33:45 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-17 01:33:45 (2235) [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-06-17 01:33:45 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-17 01:33:45 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-17 01:33:45 (6591) [INFO] 
* 2024-06-17 01:33:52 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-17 01:33:52 (6621) [INFO] 
* 2024-06-17 01:33:53 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-17 01:33:53 (730) [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.

* 2024-06-17 01:34:08 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-17 01:34:08 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-17 01:34:08 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-17 01:34:08 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-17 01:34:08 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-17 01:34:08 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-17 01:34:08 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-17 01:34:08 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-17 01:34:08 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-17 01:34:12 (1985) [WARN] Initial run of "yum makecache" failed: https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-17 01:34:12 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-17 01:34:12 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-17 01:34:12 (6591) [INFO] 
* 2024-06-17 01:34:12 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-17 01:34:12 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-17 01:34:12 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-17 01:34:12 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-17 01:34:12 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-17 01:34:12 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-17 01:34:12 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-17 01:34:12 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-17 01:34:12 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-17 01:34:12 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-17 01:34:12 (6621) [INFO] 
* 2024-06-17 01:34:27 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-17 01:34:27 (1996) [ERROR] https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-17 01:34:27 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-17 01:34:27 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i0Et07hErx/ea_profile.json
* 2024-06-17 01:34:31 (353) [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/i0Et07hErx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-17 01:34:31 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-18 01:33:51 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-18 01:33:51 (7840) [INFO] Script is up to date.
* 2024-06-18 01:33:52 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-18 01:33:52 (2235) [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-06-18 01:33:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-18 01:33:53 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-18 01:33:53 (6591) [INFO] 
* 2024-06-18 01:34:00 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-18 01:34:00 (6621) [INFO] 
* 2024-06-18 01:34:01 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-18 01:34:01 (730) [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.

* 2024-06-18 01:34:05 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-18 01:34:05 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-18 01:34:05 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-18 01:34:05 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-18 01:34:05 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-18 01:34:05 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-18 01:34:05 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-18 01:34:05 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-18 01:34:05 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-18 01:34:09 (1985) [WARN] Initial run of "yum makecache" failed: https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-18 01:34:09 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-18 01:34:09 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-18 01:34:09 (6591) [INFO] 
* 2024-06-18 01:34:09 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-18 01:34:10 (6604) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 565282.
* 2024-06-18 01:34:10 (6604) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-06-18 01:34:10 (6604) [INFO]   The other application is: yum
* 2024-06-18 01:34:10 (6604) [INFO]     Memory :  34 M RSS (325 MB VSZ)
* 2024-06-18 01:34:10 (6604) [INFO]     Started: Tue Jun 18 01:34:02 2024 - 00:08 ago
* 2024-06-18 01:34:10 (6604) [INFO]     State  : Sleeping, pid: 565282
* 2024-06-18 01:34:12 (6604) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-06-18 01:34:12 (6604) [INFO]   The other application is: yum
* 2024-06-18 01:34:12 (6604) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-06-18 01:34:12 (6604) [INFO]     Started: Tue Jun 18 01:34:02 2024 - 00:10 ago
* 2024-06-18 01:34:12 (6604) [INFO]     State  : Sleeping, pid: 565282
* 2024-06-18 01:34:14 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-18 01:34:14 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-18 01:34:14 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-18 01:34:14 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-18 01:34:14 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-18 01:34:14 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-18 01:34:14 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-18 01:34:14 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-18 01:34:14 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-18 01:34:14 (6621) [INFO] 
* 2024-06-18 01:34:20 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-18 01:34:20 (1996) [ERROR] https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-18 01:34:21 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-18 01:34:21 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6VAWytPCnr/ea_profile.json
* 2024-06-18 01:34:27 (353) [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/6VAWytPCnr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-18 01:34:27 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-19 01:33:37 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-19 01:33:37 (7840) [INFO] Script is up to date.
* 2024-06-19 01:33:38 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-19 01:33:38 (2235) [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-06-19 01:33:38 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-19 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-19 01:33:38 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-19 01:33:38 (6591) [INFO] 
* 2024-06-19 01:33:43 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-19 01:33:43 (6621) [INFO] 
* 2024-06-19 01:33:44 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-19 01:33:44 (730) [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.

* 2024-06-19 01:33:57 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-19 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-19 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-19 01:33:57 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-19 01:33:57 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-19 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-19 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-19 01:33:57 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-19 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-19 01:34:02 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-19 01:34:02 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-19 01:34:02 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-19 01:34:02 (6591) [INFO] 
* 2024-06-19 01:34:02 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-19 01:34:02 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-19 01:34:02 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-19 01:34:02 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-19 01:34:02 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-19 01:34:02 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-19 01:34:02 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-19 01:34:02 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-19 01:34:02 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-19 01:34:02 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-19 01:34:02 (6621) [INFO] 
* 2024-06-19 01:34:10 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-19 01:34:10 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-19 01:34:10 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-19 01:34:10 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/si4Cthhv2R/ea_profile.json
* 2024-06-19 01:34:15 (353) [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/si4Cthhv2R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-19 01:34:15 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-20 01:33:37 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-20 01:33:37 (7840) [INFO] Script is up to date.
* 2024-06-20 01:33:38 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-20 01:33:38 (2235) [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-06-20 01:33:38 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-20 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-20 01:33:38 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-20 01:33:38 (6591) [INFO] 
* 2024-06-20 01:33:43 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-20 01:33:43 (6621) [INFO] 
* 2024-06-20 01:33:43 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-20 01:33:43 (730) [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.

* 2024-06-20 01:33:52 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-20 01:33:52 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-20 01:33:52 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-20 01:33:52 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-20 01:33:52 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-20 01:33:52 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-20 01:33:52 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-20 01:33:52 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-20 01:33:52 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-20 01:33:55 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-20 01:33:55 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-20 01:33:55 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-20 01:33:55 (6591) [INFO] 
* 2024-06-20 01:33:56 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-20 01:33:56 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-20 01:33:56 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-20 01:33:56 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-20 01:33:56 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-20 01:33:56 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-20 01:33:56 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-20 01:33:56 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-20 01:33:56 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-20 01:33:56 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-20 01:33:56 (6621) [INFO] 
* 2024-06-20 01:34:02 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-20 01:34:02 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-20 01:34:02 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-20 01:34:02 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ce8IGcblea/ea_profile.json
* 2024-06-20 01:34:07 (353) [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/Ce8IGcblea/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-20 01:34:07 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-21 01:33:34 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-21 01:33:35 (7840) [INFO] Script is up to date.
* 2024-06-21 01:33:35 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-21 01:33:36 (2235) [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-06-21 01:33:36 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-21 01:33:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-21 01:33:36 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-21 01:33:36 (6591) [INFO] 
* 2024-06-21 01:33:41 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-21 01:33:42 (6621) [INFO] 
* 2024-06-21 01:33:42 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-21 01:33:42 (730) [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.

* 2024-06-21 01:33:57 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-21 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-21 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-21 01:33:57 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-21 01:33:57 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-21 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-21 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-21 01:33:57 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-21 01:33:57 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-21 01:34:01 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-21 01:34:01 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-21 01:34:01 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-21 01:34:01 (6591) [INFO] 
* 2024-06-21 01:34:01 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-21 01:34:02 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-21 01:34:02 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-21 01:34:02 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-21 01:34:02 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-21 01:34:02 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-21 01:34:02 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-21 01:34:02 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-21 01:34:02 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-21 01:34:02 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-21 01:34:02 (6621) [INFO] 
* 2024-06-21 01:34:10 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-21 01:34:10 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-21 01:34:10 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-21 01:34:10 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7hgk5bHLVC/ea_profile.json
* 2024-06-21 01:34:14 (353) [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/7hgk5bHLVC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-21 01:34:14 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-22 01:34:58 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-22 01:34:59 (7840) [INFO] Script is up to date.
* 2024-06-22 01:34:59 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-22 01:35:00 (2235) [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-06-22 01:35:00 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-22 01:35:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-22 01:35:00 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-22 01:35:00 (6591) [INFO] 
* 2024-06-22 01:35:09 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-22 01:35:09 (6621) [INFO] 
* 2024-06-22 01:35:09 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-22 01:35:09 (730) [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.

* 2024-06-22 01:35:21 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-22 01:35:21 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-22 01:35:21 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-22 01:35:21 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-22 01:35:21 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-22 01:35:21 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-22 01:35:21 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-22 01:35:21 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-22 01:35:21 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-22 01:35:26 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-22 01:35:26 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-22 01:35:26 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-22 01:35:26 (6591) [INFO] 
* 2024-06-22 01:35:26 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-22 01:35:26 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-22 01:35:26 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-22 01:35:26 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-22 01:35:26 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-22 01:35:26 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-22 01:35:26 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-22 01:35:26 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-22 01:35:26 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-22 01:35:26 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-22 01:35:26 (6621) [INFO] 
* 2024-06-22 01:35:32 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-22 01:35:32 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-22 01:35:32 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-22 01:35:32 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7tfVPE8jD3/ea_profile.json
* 2024-06-22 01:35:37 (353) [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/7tfVPE8jD3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-22 01:35:37 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-23 01:35:09 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-23 01:35:09 (7840) [INFO] Script is up to date.
* 2024-06-23 01:35:10 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-23 01:35:10 (2235) [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-06-23 01:35:10 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-23 01:35:10 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-23 01:35:10 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-23 01:35:10 (6591) [INFO] 
* 2024-06-23 01:35:17 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-23 01:35:17 (6621) [INFO] 
* 2024-06-23 01:35:17 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-23 01:35:17 (730) [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.

* 2024-06-23 01:35:30 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-23 01:35:30 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-23 01:35:30 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-23 01:35:30 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-23 01:35:30 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-23 01:35:30 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-23 01:35:30 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-23 01:35:30 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-23 01:35:30 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-23 01:35:35 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-23 01:35:35 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-23 01:35:35 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-23 01:35:35 (6591) [INFO] 
* 2024-06-23 01:35:35 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-23 01:35:35 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-23 01:35:35 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-23 01:35:35 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-23 01:35:35 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-23 01:35:35 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-23 01:35:35 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-23 01:35:35 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-23 01:35:35 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-23 01:35:35 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-23 01:35:35 (6621) [INFO] 
* 2024-06-23 01:35:41 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-23 01:35:41 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-23 01:35:41 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-23 01:35:41 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YL_2dVhCEZ/ea_profile.json
* 2024-06-23 01:35:46 (353) [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/YL_2dVhCEZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-23 01:35:46 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-24 01:34:17 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-24 01:34:17 (7840) [INFO] Script is up to date.
* 2024-06-24 01:34:18 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-24 01:34:18 (2235) [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-06-24 01:34:18 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-24 01:34:19 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-24 01:34:19 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-24 01:34:19 (6591) [INFO] 
* 2024-06-24 01:34:23 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-24 01:34:24 (6621) [INFO] 
* 2024-06-24 01:34:25 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-24 01:34:25 (730) [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.

* 2024-06-24 01:34:36 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-24 01:34:36 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-24 01:34:36 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-24 01:34:36 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-24 01:34:36 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-24 01:34:36 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-24 01:34:36 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-24 01:34:36 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-24 01:34:36 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-24 01:34:40 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-24 01:34:40 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-24 01:34:40 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-24 01:34:40 (6591) [INFO] 
* 2024-06-24 01:34:40 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-24 01:34:40 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-24 01:34:40 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-24 01:34:40 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-24 01:34:40 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-24 01:34:40 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-24 01:34:40 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-24 01:34:40 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-24 01:34:40 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-24 01:34:40 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-24 01:34:40 (6621) [INFO] 
* 2024-06-24 01:34:46 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-24 01:34:46 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-24 01:34:46 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-24 01:34:46 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MM2CXF_mA1/ea_profile.json
* 2024-06-24 01:34:52 (353) [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/MM2CXF_mA1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-24 01:34:52 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-25 01:33:46 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-25 01:33:46 (7840) [INFO] Script is up to date.
* 2024-06-25 01:33:47 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-25 01:33:47 (2235) [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-06-25 01:33:47 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-25 01:33:48 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-25 01:33:48 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-25 01:33:48 (6591) [INFO] 
* 2024-06-25 01:33:56 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-25 01:33:56 (6621) [INFO] 
* 2024-06-25 01:33:56 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-25 01:33:56 (730) [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.

* 2024-06-25 01:34:15 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-25 01:34:15 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-25 01:34:15 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-25 01:34:15 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-25 01:34:15 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-25 01:34:15 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-25 01:34:15 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-25 01:34:15 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-25 01:34:15 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-25 01:34:20 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-25 01:34:20 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-25 01:34:20 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-25 01:34:20 (6591) [INFO] 
* 2024-06-25 01:34:20 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-25 01:34:20 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-25 01:34:20 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-25 01:34:20 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-25 01:34:20 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-25 01:34:20 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-25 01:34:20 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-25 01:34:20 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-25 01:34:20 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-25 01:34:20 (6604) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-25 01:34:20 (6621) [INFO] 
* 2024-06-25 01:34:28 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-25 01:34:28 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-25 01:34:28 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-25 01:34:28 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d7BY28jICI/ea_profile.json
* 2024-06-25 01:34:32 (353) [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/d7BY28jICI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-25 01:34:32 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-26 01:33:34 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-26 01:33:34 (7840) [INFO] Script is up to date.
* 2024-06-26 01:33:35 (202) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-26 01:33:35 (2235) [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-06-26 01:33:35 (202) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-26 01:33:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-26 01:33:35 (202) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.34) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.35.

* 2024-06-26 01:33:35 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-26 01:33:35 (6591) [INFO] 
* 2024-06-26 01:33:45 (6604) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-26 01:33:45 (6621) [INFO] 
* 2024-06-26 01:33:45 (723) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-26 01:33:45 (730) [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.

* 2024-06-26 01:33:58 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-26 01:33:58 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-26 01:33:58 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-26 01:33:58 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-26 01:33:58 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-26 01:33:58 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-26 01:33:58 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-26 01:33:58 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-26 01:33:58 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-26 01:34:02 (1985) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 386253.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  34 M RSS (325 MB VSZ)
    Started: Wed Jun 26 01:33:57 2024 - 00:01 ago
    State  : Sleeping, pid: 386253


 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-06-26 01:34:02 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-26 01:34:02 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-26 01:34:02 (6591) [INFO] 
* 2024-06-26 01:34:03 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-26 01:34:03 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-26 01:34:03 (6604) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-26 01:34:03 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-26 01:34:03 (6604) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-26 01:34:03 (6604) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-26 01:34:03 (6604) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-26 01:34:03 (6604) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-26 01:34:03 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-26 01:34:03 (6604) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details)
* 2024-06-26 01:34:03 (6621) [INFO] 
* 2024-06-26 01:34:07 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-26 01:34:07 (1996) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-06-26 01:34:08 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-26 01:34:08 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vUsxWPQBT3/ea_profile.json
* 2024-06-26 01:34:08 (353) [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/vUsxWPQBT3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-26 01:34:08 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-27 01:34:49 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-27 01:34:49 (7823) [INFO] Newer version of script found. Downloading.
* 2024-06-27 01:34:50 (7832) [INFO] Script update to version 43 successful.
* 2024-06-27 01:34:51 (207) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-27 01:34:51 (2235) [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-06-27 01:34:51 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-27 01:34:51 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-27 01:34:51 (6738) [INFO] 
* 2024-06-27 01:34:56 (6751) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-27 01:34:56 (6768) [INFO] 
* 2024-06-27 01:34:56 (726) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-27 01:34:56 (733) [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.

* 2024-06-27 01:35:04 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-27 01:35:04 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-27 01:35:04 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-27 01:35:04 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-27 01:35:04 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-27 01:35:04 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-27 01:35:04 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-27 01:35:04 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-27 01:35:04 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-27 01:35:10 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-27 01:35:10 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-27 01:35:10 (6737) [INFO] Running: /usr/bin/yum clean all
* 2024-06-27 01:35:10 (6738) [INFO] 
* 2024-06-27 01:35:10 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-27 01:35:10 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-27 01:35:10 (6751) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-27 01:35:10 (6751) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-27 01:35:10 (6751) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-27 01:35:10 (6751) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-27 01:35:10 (6751) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-27 01:35:10 (6751) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-27 01:35:10 (6751) [INFO] Cleaning up list of fastest mirrors
* 2024-06-27 01:35:10 (6751) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-27 01:35:10 (6768) [INFO] 
* 2024-06-27 01:35:16 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-27 01:35:16 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-27 01:35:16 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-27 01:35:18 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bpGes_NtxF/ea_profile.json
* 2024-06-27 01:35:24 (356) [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/bpGes_NtxF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-27 01:35:24 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-28 01:33:59 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-28 01:33:59 (7994) [INFO] Script is up to date.
* 2024-06-28 01:34:00 (207) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-28 01:34:00 (2235) [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-06-28 01:34:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-28 01:34:00 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-28 01:34:00 (6738) [INFO] 
* 2024-06-28 01:34:07 (6751) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-28 01:34:07 (6768) [INFO] 
* 2024-06-28 01:34:07 (726) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-28 01:34:07 (733) [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.

* 2024-06-28 01:34:16 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-28 01:34:16 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-28 01:34:16 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-28 01:34:16 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-28 01:34:16 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-28 01:34:16 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-28 01:34:16 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-28 01:34:16 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-28 01:34:16 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-28 01:34:20 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-28 01:34:20 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-28 01:34:20 (6737) [INFO] Running: /usr/bin/yum clean all
* 2024-06-28 01:34:20 (6738) [INFO] 
* 2024-06-28 01:34:21 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-28 01:34:21 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-28 01:34:21 (6751) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-28 01:34:21 (6751) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-28 01:34:21 (6751) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-28 01:34:21 (6751) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-28 01:34:21 (6751) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-28 01:34:21 (6751) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-28 01:34:21 (6751) [INFO] Cleaning up list of fastest mirrors
* 2024-06-28 01:34:21 (6751) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-28 01:34:21 (6768) [INFO] 
* 2024-06-28 01:34:25 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-28 01:34:25 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-28 01:34:25 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-28 01:34:27 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BGZj8j8vYl/ea_profile.json
* 2024-06-28 01:34:31 (356) [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/BGZj8j8vYl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-28 01:34:31 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-29 01:35:03 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-29 01:35:03 (7994) [INFO] Script is up to date.
* 2024-06-29 01:35:04 (207) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-29 01:35:04 (2235) [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-06-29 01:35:04 (207) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-29 01:35:04 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-29 01:35:04 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-29 01:35:04 (6738) [INFO] 
* 2024-06-29 01:35:09 (6751) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-29 01:35:09 (6768) [INFO] 
* 2024-06-29 01:35:10 (726) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-29 01:35:10 (733) [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.

* 2024-06-29 01:35:24 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-29 01:35:24 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-29 01:35:24 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-29 01:35:24 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-29 01:35:24 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-29 01:35:24 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-29 01:35:24 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-29 01:35:24 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-29 01:35:24 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-29 01:35:29 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-29 01:35:29 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-29 01:35:29 (6737) [INFO] Running: /usr/bin/yum clean all
* 2024-06-29 01:35:29 (6738) [INFO] 
* 2024-06-29 01:35:29 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-29 01:35:29 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-29 01:35:29 (6751) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-29 01:35:29 (6751) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-29 01:35:29 (6751) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-29 01:35:29 (6751) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-29 01:35:29 (6751) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-29 01:35:29 (6751) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-29 01:35:29 (6751) [INFO] Cleaning up list of fastest mirrors
* 2024-06-29 01:35:29 (6751) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-29 01:35:29 (6768) [INFO] 
* 2024-06-29 01:35:35 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-29 01:35:35 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-29 01:35:36 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-29 01:35:37 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nG1es1JjX_/ea_profile.json
* 2024-06-29 01:35:42 (356) [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/nG1es1JjX_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-29 01:35:42 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-30 01:35:14 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-30 01:35:14 (7994) [INFO] Script is up to date.
* 2024-06-30 01:35:15 (207) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-06-30 01:35:15 (2235) [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-06-30 01:35:15 (207) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-06-30 01:35:15 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-06-30 01:35:15 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-30 01:35:15 (6738) [INFO] 
* 2024-06-30 01:35:22 (6751) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-30 01:35:22 (6768) [INFO] 
* 2024-06-30 01:35:22 (726) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-06-30 01:35:22 (733) [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.

* 2024-06-30 01:35:23 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-06-30 01:35:23 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-06-30 01:35:23 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-06-30 01:35:23 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-30 01:35:23 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-06-30 01:35:23 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-06-30 01:35:23 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-06-30 01:35:23 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-06-30 01:35:23 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-06-30 01:35:27 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-30 01:35:27 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-30 01:35:27 (6737) [INFO] Running: /usr/bin/yum clean all
* 2024-06-30 01:35:27 (6738) [INFO] 
* 2024-06-30 01:35:27 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-30 01:35:27 (6751) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 21646.
* 2024-06-30 01:35:27 (6751) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-06-30 01:35:27 (6751) [INFO]   The other application is: yum
* 2024-06-30 01:35:27 (6751) [INFO]     Memory :  35 M RSS (325 MB VSZ)
* 2024-06-30 01:35:27 (6751) [INFO]     Started: Sun Jun 30 01:35:22 2024 - 00:05 ago
* 2024-06-30 01:35:27 (6751) [INFO]     State  : Sleeping, pid: 21646
* 2024-06-30 01:35:29 (6751) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-06-30 01:35:29 (6751) [INFO]   The other application is: yum
* 2024-06-30 01:35:29 (6751) [INFO]     Memory :  38 M RSS (331 MB VSZ)
* 2024-06-30 01:35:29 (6751) [INFO]     Started: Sun Jun 30 01:35:22 2024 - 00:07 ago
* 2024-06-30 01:35:29 (6751) [INFO]     State  : Uninterruptible, pid: 21646
* 2024-06-30 01:35:31 (6751) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-06-30 01:35:31 (6751) [INFO]   The other application is: yum
* 2024-06-30 01:35:31 (6751) [INFO]     Memory :  39 M RSS (332 MB VSZ)
* 2024-06-30 01:35:31 (6751) [INFO]     Started: Sun Jun 30 01:35:22 2024 - 00:09 ago
* 2024-06-30 01:35:31 (6751) [INFO]     State  : Sleeping, pid: 21646
* 2024-06-30 01:35:33 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-06-30 01:35:33 (6751) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-06-30 01:35:33 (6751) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-30 01:35:33 (6751) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-06-30 01:35:33 (6751) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-06-30 01:35:33 (6751) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-06-30 01:35:33 (6751) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-06-30 01:35:33 (6751) [INFO] Cleaning up list of fastest mirrors
* 2024-06-30 01:35:33 (6751) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-06-30 01:35:33 (6768) [INFO] 
* 2024-06-30 01:35:39 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-30 01:35:39 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-06-30 01:35:39 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-30 01:35:41 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OBnSWr_Jzj/ea_profile.json
* 2024-06-30 01:35:45 (356) [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/OBnSWr_Jzj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-30 01:35:45 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-01 01:33:51 (7972) [INFO] Self-update of script version 43 requested.
* 2024-07-01 01:33:51 (7994) [INFO] Script is up to date.
* 2024-07-01 01:33:52 (207) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-01 01:33:52 (2235) [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-01 01:33:52 (207) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-01 01:33:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-01 01:33:52 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-01 01:33:52 (6738) [INFO] 
* 2024-07-01 01:33:56 (6751) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-01 01:33:56 (6768) [INFO] 
* 2024-07-01 01:33:56 (726) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-01 01:33:56 (733) [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.

* 2024-07-01 01:34:06 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-01 01:34:06 (2122) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-01 01:34:06 (2122) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-01 01:34:06 (2100) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-01 01:34:06 (2100) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-01 01:34:06 (2122) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-01 01:34:06 (2122) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-01 01:34:06 (2100) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-01 01:34:06 (2122) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-01 01:34:10 (1985) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-01 01:34:10 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-01 01:34:10 (6737) [INFO] Running: /usr/bin/yum clean all
* 2024-07-01 01:34:10 (6738) [INFO] 
* 2024-07-01 01:34:10 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-01 01:34:11 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-01 01:34:11 (6751) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-07-01 01:34:11 (6751) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-01 01:34:11 (6751) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-07-01 01:34:11 (6751) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-07-01 01:34:11 (6751) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-07-01 01:34:11 (6751) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-07-01 01:34:11 (6751) [INFO] Cleaning up list of fastest mirrors
* 2024-07-01 01:34:11 (6751) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-07-01 01:34:11 (6768) [INFO] 
* 2024-07-01 01:34:17 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-01 01:34:17 (1996) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-01 01:34:17 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-01 01:34:19 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZGbrblEj1P/ea_profile.json
* 2024-07-01 01:34:24 (356) [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/ZGbrblEj1P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-07-01 01:34:24 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-02 01:34:36 (7972) [INFO] Self-update of script version 43 requested.
* 2024-07-02 01:34:36 (7977) [INFO] Newer version of script found. Downloading.
* 2024-07-02 01:34:37 (7986) [INFO] Script update to version 44 successful.
* 2024-07-02 01:34:38 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-02 01:34:38 (2236) [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-02 01:34:38 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-02 01:34:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-02 01:34:38 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-02 01:34:38 (6800) [INFO] 
* 2024-07-02 01:34:47 (6813) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 27, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-02 01:34:47 (6830) [INFO] 
* 2024-07-02 01:34:47 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-02 01:34:47 (734) [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.

* 2024-07-02 01:35:05 (2101) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-02 01:35:05 (2123) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-02 01:35:05 (2123) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-02 01:35:05 (2101) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-02 01:35:05 (2101) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-02 01:35:05 (2123) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-02 01:35:05 (2123) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-02 01:35:05 (2101) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-02 01:35:05 (2123) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-02 01:35:13 (1986) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-02 01:35:13 (1987) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-02 01:35:13 (6799) [INFO] Running: /usr/bin/yum clean all
* 2024-07-02 01:35:13 (6800) [INFO] 
* 2024-07-02 01:35:13 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-02 01:35:13 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-02 01:35:13 (6813) [INFO]               : docker-ce-stable epel extras imunify360 imunify360-rollout-1
* 2024-07-02 01:35:13 (6813) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-02 01:35:13 (6813) [INFO]               : mongodb-org-4.0 mongodb-org-5.0 mysql-connectors-community
* 2024-07-02 01:35:13 (6813) [INFO]               : mysql-tools-community mysql57-community nodesource remi-php72
* 2024-07-02 01:35:13 (6813) [INFO]               : remi-php73 remi-safe updates virtualbox wp-toolkit-cpanel
* 2024-07-02 01:35:13 (6813) [INFO]               : wp-toolkit-thirdparties yarn
* 2024-07-02 01:35:13 (6813) [INFO] Cleaning up list of fastest mirrors
* 2024-07-02 01:35:13 (6813) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-07-02 01:35:13 (6830) [INFO] 
* 2024-07-02 01:35:20 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-02 01:35:20 (1997) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-02 01:35:20 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-02 01:35:22 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZCqtKUAgLe/ea_profile.json
* 2024-07-02 01:35:29 (357) [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/ZCqtKUAgLe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-02 01:35:29 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-03 01:33:29 (8035) [INFO] Self-update of script version 44 requested.
* 2024-07-03 01:33:29 (8057) [INFO] Script is up to date.
* 2024-07-03 01:33:30 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-03 01:33:31 (2236) [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-03 01:33:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-03 01:33:31 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-03 01:33:31 (6800) [INFO] 
* 2024-07-03 01:33:35 (6813) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-03 01:33:35 (6830) [INFO] 
* 2024-07-03 01:33:35 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-03 01:33:35 (734) [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.

* 2024-07-03 01:33:39 (2101) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2101) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-03 01:33:39 (2101) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-03 01:33:39 (2101) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-03 01:33:39 (2123) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-03 01:33:44 (1986) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-03 01:33:44 (1987) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-03 01:33:44 (6799) [INFO] Running: /usr/bin/yum clean all
* 2024-07-03 01:33:44 (6800) [INFO] 
* 2024-07-03 01:33:45 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-03 01:33:45 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-03 01:33:45 (6813) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-03 01:33:45 (6813) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-03 01:33:45 (6813) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-03 01:33:45 (6813) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-03 01:33:45 (6813) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-03 01:33:45 (6813) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-03 01:33:45 (6813) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-03 01:33:45 (6813) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-03 01:33:45 (6813) [INFO]               : yarn
* 2024-07-03 01:33:45 (6813) [INFO] Cleaning up list of fastest mirrors
* 2024-07-03 01:33:45 (6813) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-03 01:33:45 (6830) [INFO] 
* 2024-07-03 01:33:52 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-03 01:33:52 (1997) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-03 01:33:52 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-03 01:33:54 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Xpng_wQam1/ea_profile.json
* 2024-07-03 01:33:58 (357) [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/Xpng_wQam1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-03 01:33:58 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-04 01:34:01 (8035) [INFO] Self-update of script version 44 requested.
* 2024-07-04 01:34:01 (8040) [INFO] Newer version of script found. Downloading.
* 2024-07-04 01:34:01 (8049) [INFO] Script update to version 45 successful.
* 2024-07-04 01:34:02 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-04 01:34:03 (2249) [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-04 01:34:03 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-04 01:34:03 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-04 01:34:03 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-04 01:34:03 (6814) [INFO] 
* 2024-07-04 01:34:11 (6827) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-04 01:34:11 (6844) [INFO] 
* 2024-07-04 01:34:12 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-04 01:34:12 (734) [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.

* 2024-07-04 01:34:21 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-04 01:34:21 (2114) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-04 01:34:21 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-04 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-04 01:34:28 (1999) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-04 01:34:28 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-04 01:34:28 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-04 01:34:28 (6814) [INFO] 
* 2024-07-04 01:34:28 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-04 01:34:28 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-04 01:34:28 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-04 01:34:28 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-04 01:34:28 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-04 01:34:28 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-04 01:34:28 (6827) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-04 01:34:28 (6827) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-04 01:34:28 (6827) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-04 01:34:28 (6827) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-04 01:34:28 (6827) [INFO]               : yarn
* 2024-07-04 01:34:28 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-04 01:34:28 (6827) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-04 01:34:28 (6844) [INFO] 
* 2024-07-04 01:34:34 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-04 01:34:34 (2010) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-04 01:34:34 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-04 01:34:35 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NfrBaSU_9F/ea_profile.json
* 2024-07-04 01:34:39 (357) [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/NfrBaSU_9F/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-04 01:34:39 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-05 01:35:30 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-05 01:35:30 (8071) [INFO] Script is up to date.
* 2024-07-05 01:35:32 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-05 01:35:32 (2249) [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-05 01:35:32 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-05 01:35:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-05 01:35:32 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-05 01:35:32 (6814) [INFO] 
* 2024-07-05 01:35:38 (6827) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-05 01:35:38 (6844) [INFO] 
* 2024-07-05 01:35:38 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-05 01:35:38 (734) [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.

* 2024-07-05 01:35:45 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-05 01:35:45 (2114) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-05 01:35:45 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-05 01:35:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-05 01:36:01 (1999) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 834483.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Fri Jul  5 01:35:44 2024 - 00:01 ago
    State  : Sleeping, pid: 834483
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Fri Jul  5 01:35:44 2024 - 00:03 ago
    State  : Sleeping, pid: 834483
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Fri Jul  5 01:35:44 2024 - 00:05 ago
    State  : Sleeping, pid: 834483
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Fri Jul  5 01:35:44 2024 - 00:07 ago
    State  : Sleeping, pid: 834483
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (334 MB VSZ)
    Started: Fri Jul  5 01:35:44 2024 - 00:09 ago
    State  : Uninterruptible, pid: 834483
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-05 01:36:01 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-05 01:36:01 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-05 01:36:01 (6814) [INFO] 
* 2024-07-05 01:36:02 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-05 01:36:02 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-05 01:36:02 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-05 01:36:02 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-05 01:36:02 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-05 01:36:02 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-05 01:36:02 (6827) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-05 01:36:02 (6827) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-05 01:36:02 (6827) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-05 01:36:02 (6827) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-05 01:36:02 (6827) [INFO]               : yarn
* 2024-07-05 01:36:02 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-05 01:36:02 (6827) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-05 01:36:02 (6844) [INFO] 
* 2024-07-05 01:36:14 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-05 01:36:14 (2010) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-05 01:36:14 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-05 01:36:15 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ErIUeMWIft/ea_profile.json
* 2024-07-05 01:36:22 (357) [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/ErIUeMWIft/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-05 01:36:22 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-06 01:35:35 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-06 01:35:35 (8071) [INFO] Script is up to date.
* 2024-07-06 01:35:36 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-06 01:35:36 (2249) [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-06 01:35:36 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-06 01:35:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-06 01:35:36 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-06 01:35:36 (6814) [INFO] 
* 2024-07-06 01:35:44 (6827) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-06 01:35:44 (6844) [INFO] 
* 2024-07-06 01:35:45 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-06 01:35:45 (734) [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.

* 2024-07-06 01:35:52 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-06 01:35:52 (2114) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-06 01:35:52 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-06 01:35:52 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-06 01:35:57 (1999) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-06 01:35:57 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-06 01:35:57 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-06 01:35:57 (6814) [INFO] 
* 2024-07-06 01:35:57 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-06 01:35:58 (6827) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 150044.
* 2024-07-06 01:35:58 (6827) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-07-06 01:35:58 (6827) [INFO]   The other application is: yum
* 2024-07-06 01:35:58 (6827) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-07-06 01:35:58 (6827) [INFO]     Started: Sat Jul  6 01:35:50 2024 - 00:08 ago
* 2024-07-06 01:35:58 (6827) [INFO]     State  : Sleeping, pid: 150044
* 2024-07-06 01:36:00 (6827) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-07-06 01:36:00 (6827) [INFO]   The other application is: yum
* 2024-07-06 01:36:00 (6827) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-07-06 01:36:00 (6827) [INFO]     Started: Sat Jul  6 01:35:50 2024 - 00:10 ago
* 2024-07-06 01:36:00 (6827) [INFO]     State  : Sleeping, pid: 150044
* 2024-07-06 01:36:02 (6827) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-07-06 01:36:02 (6827) [INFO]   The other application is: yum
* 2024-07-06 01:36:02 (6827) [INFO]     Memory :  40 M RSS (334 MB VSZ)
* 2024-07-06 01:36:02 (6827) [INFO]     Started: Sat Jul  6 01:35:50 2024 - 00:12 ago
* 2024-07-06 01:36:02 (6827) [INFO]     State  : Sleeping, pid: 150044
* 2024-07-06 01:36:04 (6827) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-07-06 01:36:04 (6827) [INFO]   The other application is: yum
* 2024-07-06 01:36:04 (6827) [INFO]     Memory :  40 M RSS (334 MB VSZ)
* 2024-07-06 01:36:04 (6827) [INFO]     Started: Sat Jul  6 01:35:50 2024 - 00:14 ago
* 2024-07-06 01:36:04 (6827) [INFO]     State  : Uninterruptible, pid: 150044
* 2024-07-06 01:36:06 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-06 01:36:06 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-06 01:36:06 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-06 01:36:06 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-06 01:36:06 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-06 01:36:06 (6827) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-06 01:36:06 (6827) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-06 01:36:06 (6827) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-06 01:36:06 (6827) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-06 01:36:06 (6827) [INFO]               : yarn
* 2024-07-06 01:36:06 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-06 01:36:06 (6827) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-06 01:36:06 (6844) [INFO] 
* 2024-07-06 01:36:15 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-06 01:36:15 (2010) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-06 01:36:15 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-06 01:36:17 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BRk7fV6DC6/ea_profile.json
* 2024-07-06 01:36:24 (357) [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/BRk7fV6DC6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-06 01:36:24 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-07 01:34:57 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-07 01:34:57 (8071) [INFO] Script is up to date.
* 2024-07-07 01:34:58 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-07 01:34:58 (2249) [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-07 01:34:58 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-07 01:34:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-07 01:34:58 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-07 01:34:58 (6814) [INFO] 
* 2024-07-07 01:35:04 (6827) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-07 01:35:04 (6844) [INFO] 
* 2024-07-07 01:35:04 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-07 01:35:04 (734) [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.

* 2024-07-07 01:35:13 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-07 01:35:13 (2114) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-07 01:35:13 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-07 01:35:13 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-07 01:35:18 (1999) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-07 01:35:18 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-07 01:35:18 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-07 01:35:18 (6814) [INFO] 
* 2024-07-07 01:35:19 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-07 01:35:19 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-07 01:35:19 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-07 01:35:19 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-07 01:35:19 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-07 01:35:19 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-07 01:35:19 (6827) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-07 01:35:19 (6827) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-07 01:35:19 (6827) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-07 01:35:19 (6827) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-07 01:35:19 (6827) [INFO]               : yarn
* 2024-07-07 01:35:19 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-07 01:35:19 (6827) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-07 01:35:19 (6844) [INFO] 
* 2024-07-07 01:35:25 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-07 01:35:25 (2010) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-07 01:35:25 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-07 01:35:26 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Mhgtv1UWiY/ea_profile.json
* 2024-07-07 01:35:31 (357) [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/Mhgtv1UWiY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-07 01:35:31 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-08 01:33:29 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-08 01:33:29 (8071) [INFO] Script is up to date.
* 2024-07-08 01:33:30 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-08 01:33:30 (2249) [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-08 01:33:30 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-08 01:33:30 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-08 01:33:30 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-08 01:33:30 (6814) [INFO] 
* 2024-07-08 01:33:35 (6827) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-08 01:33:35 (6844) [INFO] 
* 2024-07-08 01:33:35 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-08 01:33:35 (734) [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.

* 2024-07-08 01:33:45 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-08 01:33:45 (2114) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-08 01:33:45 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-08 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-08 01:33:51 (1999) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-08 01:33:51 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-08 01:33:51 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-08 01:33:51 (6814) [INFO] 
* 2024-07-08 01:33:51 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-08 01:33:51 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-08 01:33:51 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-08 01:33:51 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-08 01:33:51 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-08 01:33:51 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-08 01:33:51 (6827) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-08 01:33:51 (6827) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-08 01:33:51 (6827) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-08 01:33:51 (6827) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-08 01:33:51 (6827) [INFO]               : yarn
* 2024-07-08 01:33:51 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-08 01:33:51 (6827) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-08 01:33:51 (6844) [INFO] 
* 2024-07-08 01:33:58 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-08 01:33:58 (2010) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-08 01:33:58 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-08 01:34:00 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rpS4fthdYH/ea_profile.json
* 2024-07-08 01:34:07 (357) [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/rpS4fthdYH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-08 01:34:07 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-09 01:33:47 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-09 01:33:47 (8071) [INFO] Script is up to date.
* 2024-07-09 01:33:48 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-09 01:33:48 (2249) [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-09 01:33:48 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-09 01:33:48 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-09 01:33:49 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-09 01:33:49 (6814) [INFO] 
* 2024-07-09 01:33:53 (6827) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-09 01:33:53 (6844) [INFO] 
* 2024-07-09 01:33:54 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-09 01:33:54 (734) [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.

* 2024-07-09 01:34:12 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-09 01:34:12 (2114) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-09 01:34:12 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-09 01:34:12 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-09 01:34:21 (1999) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-09 01:34:21 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-09 01:34:21 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-09 01:34:21 (6814) [INFO] 
* 2024-07-09 01:34:21 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-09 01:34:22 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-09 01:34:22 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-09 01:34:22 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-09 01:34:22 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-09 01:34:22 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-09 01:34:22 (6827) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-09 01:34:22 (6827) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-09 01:34:22 (6827) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-09 01:34:22 (6827) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-09 01:34:22 (6827) [INFO]               : yarn
* 2024-07-09 01:34:22 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-09 01:34:22 (6827) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-09 01:34:22 (6844) [INFO] 
* 2024-07-09 01:34:29 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-09 01:34:29 (2010) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-09 01:34:29 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-09 01:34:30 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yrbU20C9ev/ea_profile.json
* 2024-07-09 01:34:35 (357) [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/yrbU20C9ev/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-09 01:34:35 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-10 01:33:45 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-10 01:33:45 (8071) [INFO] Script is up to date.
* 2024-07-10 01:33:46 (208) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-10 01:33:46 (2249) [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-10 01:33:46 (208) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-10 01:33:46 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-10 01:33:46 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-10 01:33:46 (6814) [INFO] 
* 2024-07-10 01:33:52 (6827) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-10 01:33:53 (6844) [INFO] 
* 2024-07-10 01:33:53 (727) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-10 01:33:53 (734) [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.

* 2024-07-10 01:34:09 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2114) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-10 01:34:09 (2114) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-10 01:34:09 (2114) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-10 01:34:09 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-10 01:34:32 (1999) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-10 01:34:32 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-10 01:34:32 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-10 01:34:32 (6814) [INFO] 
* 2024-07-10 01:34:32 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-10 01:34:32 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-10 01:34:32 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-10 01:34:32 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-10 01:34:32 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-10 01:34:32 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-10 01:34:32 (6827) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-10 01:34:32 (6827) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-10 01:34:32 (6827) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-10 01:34:32 (6827) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-10 01:34:32 (6827) [INFO]               : yarn
* 2024-07-10 01:34:32 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-10 01:34:32 (6827) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-10 01:34:32 (6844) [INFO] 
* 2024-07-10 01:34:40 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-10 01:34:40 (2010) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-10 01:34:40 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-10 01:34:42 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Wez04Oiche/ea_profile.json
* 2024-07-10 01:34:48 (357) [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/Wez04Oiche/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-10 01:34:48 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-11 01:33:34 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-11 01:33:34 (8054) [INFO] Newer version of script found. Downloading.
* 2024-07-11 01:33:35 (8063) [INFO] Script update to version 46 successful.
* 2024-07-11 01:33:36 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-11 01:33:36 (2278) [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-11 01:33:36 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-11 01:33:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-11 01:33:36 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-11 01:33:36 (6847) [INFO] 
* 2024-07-11 01:33:40 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-11 01:33:40 (6877) [INFO] 
* 2024-07-11 01:33:40 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-11 01:33:40 (751) [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.

* 2024-07-11 01:33:40 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-11 01:33:40 (6847) [INFO] 
* 2024-07-11 01:33:56 (6877) [INFO] 
* 2024-07-11 01:33:57 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-11 01:33:57 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-11 01:33:57 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-11 01:33:57 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-11 01:33:57 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-11 01:33:57 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-11 01:33:57 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-11 01:33:57 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-11 01:33:57 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-11 01:34:02 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-11 01:34:02 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-11 01:34:02 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-11 01:34:02 (6847) [INFO] 
* 2024-07-11 01:34:02 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-11 01:34:02 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-11 01:34:02 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-11 01:34:02 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-11 01:34:02 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-11 01:34:02 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-11 01:34:02 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-11 01:34:02 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-11 01:34:02 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-11 01:34:02 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-11 01:34:02 (6860) [INFO]               : yarn
* 2024-07-11 01:34:03 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-11 01:34:03 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-11 01:34:03 (6877) [INFO] 
* 2024-07-11 01:34:16 (2035) [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-11 01:34:16 (2036) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 924695.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Thu Jul 11 01:33:49 2024 - 00:14 ago
    State  : Sleeping, pid: 924695
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Thu Jul 11 01:33:49 2024 - 00:16 ago
    State  : Uninterruptible, pid: 924695
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Thu Jul 11 01:33:49 2024 - 00:18 ago
    State  : Sleeping, pid: 924695
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (2.7 GB VSZ)
    Started: Thu Jul 11 01:33:49 2024 - 00:20 ago
    State  : Sleeping, pid: 924695
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-11 01:34:16 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-11 01:34:17 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BrlTWrIbpt/ea_profile.json
* 2024-07-11 01:34:23 (374) [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/BrlTWrIbpt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-11 01:34:23 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-12 01:33:46 (8126) [INFO] Self-update of script version 46 requested.
* 2024-07-12 01:33:46 (8131) [INFO] Newer version of script found. Downloading.
* 2024-07-12 01:33:47 (8140) [INFO] Script update to version 47 successful.
* 2024-07-12 01:33:48 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-12 01:33:48 (2278) [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-12 01:33:48 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-12 01:33:48 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-12 01:33:48 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-12 01:33:48 (6849) [INFO] 
* 2024-07-12 01:33:54 (6862) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-12 01:33:54 (6879) [INFO] 
* 2024-07-12 01:33:55 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-12 01:33:55 (751) [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.

* 2024-07-12 01:33:55 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-12 01:33:55 (6849) [INFO] 
* 2024-07-12 01:34:25 (6879) [INFO] 
* 2024-07-12 01:34:27 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-12 01:34:27 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-12 01:34:27 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-12 01:34:27 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-12 01:34:27 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-12 01:34:27 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-12 01:34:27 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-12 01:34:27 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-12 01:34:27 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-12 01:34:33 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-12 01:34:33 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-12 01:34:33 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-12 01:34:33 (6849) [INFO] 
* 2024-07-12 01:34:33 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-12 01:34:33 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-12 01:34:33 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-12 01:34:33 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-12 01:34:33 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-12 01:34:33 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-12 01:34:33 (6862) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-12 01:34:33 (6862) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-12 01:34:33 (6862) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-12 01:34:33 (6862) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-12 01:34:33 (6862) [INFO]               : yarn
* 2024-07-12 01:34:33 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-12 01:34:33 (6862) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-12 01:34:33 (6879) [INFO] 
* 2024-07-12 01:34:41 (2035) [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-12 01:34:41 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-12 01:34:42 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-12 01:34:43 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F2ANnyL6tN/ea_profile.json
* 2024-07-12 01:34:50 (374) [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/F2ANnyL6tN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-12 01:34:50 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-13 01:35:31 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-13 01:35:31 (8150) [INFO] Script is up to date.
* 2024-07-13 01:35:32 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-13 01:35:32 (2278) [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 01:35:32 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-13 01:35:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-13 01:35:32 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-13 01:35:32 (6849) [INFO] 
* 2024-07-13 01:35:37 (6862) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-13 01:35:37 (6879) [INFO] 
* 2024-07-13 01:35:38 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-13 01:35:38 (751) [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.

* 2024-07-13 01:35:38 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-13 01:35:38 (6849) [INFO] 
* 2024-07-13 01:36:00 (6879) [INFO] 
* 2024-07-13 01:36:01 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-13 01:36:01 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-13 01:36:01 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-13 01:36:01 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-13 01:36:01 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-13 01:36:01 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-13 01:36:01 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-13 01:36:01 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-13 01:36:01 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-13 01:36:05 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-13 01:36:05 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-13 01:36:05 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-13 01:36:05 (6849) [INFO] 
* 2024-07-13 01:36:05 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-13 01:36:05 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-13 01:36:05 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-13 01:36:05 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-13 01:36:05 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-13 01:36:05 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-13 01:36:05 (6862) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-13 01:36:05 (6862) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-13 01:36:05 (6862) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-13 01:36:05 (6862) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-13 01:36:05 (6862) [INFO]               : yarn
* 2024-07-13 01:36:05 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-13 01:36:05 (6862) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-13 01:36:05 (6879) [INFO] 
* 2024-07-13 01:36:11 (2035) [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 01:36:11 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-13 01:36:12 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-13 01:36:13 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SNXQoxQHb8/ea_profile.json
* 2024-07-13 01:36:17 (374) [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/SNXQoxQHb8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-13 01:36:17 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-14 01:34:44 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-14 01:34:44 (8150) [INFO] Script is up to date.
* 2024-07-14 01:34:45 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-14 01:34:45 (2278) [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-14 01:34:45 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-14 01:34:45 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-14 01:34:45 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-14 01:34:45 (6849) [INFO] 
* 2024-07-14 01:34:50 (6862) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-14 01:34:50 (6879) [INFO] 
* 2024-07-14 01:34:51 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-14 01:34:51 (751) [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.

* 2024-07-14 01:34:51 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-14 01:34:51 (6849) [INFO] 
* 2024-07-14 01:35:12 (6879) [INFO] 
* 2024-07-14 01:35:19 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-14 01:35:19 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-14 01:35:19 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-14 01:35:19 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-14 01:35:19 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-14 01:35:19 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-14 01:35:19 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-14 01:35:19 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-14 01:35:19 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-14 01:35:24 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-14 01:35:24 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-14 01:35:24 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-14 01:35:24 (6849) [INFO] 
* 2024-07-14 01:35:24 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-14 01:35:25 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-14 01:35:25 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-14 01:35:25 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-14 01:35:25 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-14 01:35:25 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-14 01:35:25 (6862) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-14 01:35:25 (6862) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-14 01:35:25 (6862) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-14 01:35:25 (6862) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-14 01:35:25 (6862) [INFO]               : yarn
* 2024-07-14 01:35:25 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-14 01:35:25 (6862) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-14 01:35:25 (6879) [INFO] 
* 2024-07-14 01:35:33 (2035) [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-14 01:35:33 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-14 01:35:33 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-14 01:35:34 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pl5e2de8Ar/ea_profile.json
* 2024-07-14 01:35:41 (374) [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/pl5e2de8Ar/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-14 01:35:41 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-15 01:33:56 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-15 01:33:56 (8150) [INFO] Script is up to date.
* 2024-07-15 01:33:57 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-15 01:33:57 (2278) [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-15 01:33:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-15 01:33:58 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-15 01:33:58 (6849) [INFO] 
* 2024-07-15 01:34:01 (6862) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-15 01:34:02 (6879) [INFO] 
* 2024-07-15 01:34:02 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-15 01:34:02 (751) [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.

* 2024-07-15 01:34:02 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-15 01:34:02 (6849) [INFO] 
* 2024-07-15 01:34:12 (6879) [INFO] 
* 2024-07-15 01:34:13 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-15 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-15 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-15 01:34:13 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-15 01:34:13 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-15 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-15 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-15 01:34:13 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-15 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-15 01:34:18 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-15 01:34:18 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-15 01:34:18 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-15 01:34:18 (6849) [INFO] 
* 2024-07-15 01:34:18 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-15 01:34:18 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-15 01:34:18 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-15 01:34:18 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-15 01:34:18 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-15 01:34:18 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-15 01:34:18 (6862) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-15 01:34:18 (6862) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-15 01:34:18 (6862) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-15 01:34:18 (6862) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-15 01:34:18 (6862) [INFO]               : yarn
* 2024-07-15 01:34:18 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-15 01:34:18 (6862) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-15 01:34:18 (6879) [INFO] 
* 2024-07-15 01:34:26 (2035) [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-15 01:34:26 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-15 01:34:26 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-15 01:34:28 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZXjbGad2Sz/ea_profile.json
* 2024-07-15 01:34:31 (374) [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/ZXjbGad2Sz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-15 01:34:31 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-16 01:33:35 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-16 01:33:35 (8150) [INFO] Script is up to date.
* 2024-07-16 01:33:36 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-16 01:33:37 (2278) [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-16 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-16 01:33:37 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-16 01:33:37 (6849) [INFO] 
* 2024-07-16 01:33:43 (6862) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-16 01:33:43 (6879) [INFO] 
* 2024-07-16 01:33:43 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-16 01:33:43 (751) [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.

* 2024-07-16 01:33:43 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-16 01:33:43 (6849) [INFO] 
* 2024-07-16 01:34:13 (6879) [INFO] 
* 2024-07-16 01:34:16 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-16 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-16 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-16 01:34:16 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-16 01:34:16 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-16 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-16 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-16 01:34:16 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-16 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-16 01:34:23 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-16 01:34:23 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-16 01:34:23 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-16 01:34:23 (6849) [INFO] 
* 2024-07-16 01:34:23 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-16 01:34:24 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-16 01:34:24 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-16 01:34:24 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-16 01:34:24 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-16 01:34:24 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-16 01:34:24 (6862) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-16 01:34:24 (6862) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-16 01:34:24 (6862) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-16 01:34:24 (6862) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-16 01:34:24 (6862) [INFO]               : yarn
* 2024-07-16 01:34:24 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-16 01:34:24 (6862) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-16 01:34:24 (6879) [INFO] 
* 2024-07-16 01:34:42 (2035) [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-16 01:34:42 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-16 01:34:42 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-16 01:34:43 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/buRR_Gp0y0/ea_profile.json
* 2024-07-16 01:34:50 (374) [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/buRR_Gp0y0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-16 01:34:50 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-17 01:33:37 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-17 01:33:37 (8133) [INFO] Newer version of script found. Downloading.
* 2024-07-17 01:33:37 (8142) [INFO] Script update to version 48 successful.
* 2024-07-17 01:33:39 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-17 01:33:39 (2278) [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-17 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-17 01:33:39 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-17 01:33:39 (6847) [INFO] 
* 2024-07-17 01:33:47 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 29, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-17 01:33:47 (6877) [INFO] 
* 2024-07-17 01:33:47 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-17 01:33:47 (751) [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.

* 2024-07-17 01:33:47 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-17 01:33:47 (6847) [INFO] 
* 2024-07-17 01:33:54 (6877) [INFO] 
* 2024-07-17 01:33:55 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-17 01:33:55 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-17 01:33:55 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-17 01:33:55 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-17 01:33:55 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-17 01:33:55 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-17 01:33:55 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-17 01:33:55 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-17 01:33:55 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-17 01:34:00 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-17 01:34:00 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-17 01:34:00 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-17 01:34:00 (6847) [INFO] 
* 2024-07-17 01:34:00 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-17 01:34:01 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-17 01:34:01 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-17 01:34:01 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-17 01:34:01 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-17 01:34:01 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-17 01:34:01 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-17 01:34:01 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-17 01:34:01 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-17 01:34:01 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-17 01:34:01 (6860) [INFO]               : yarn
* 2024-07-17 01:34:01 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-17 01:34:01 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-17 01:34:01 (6877) [INFO] 
* 2024-07-17 01:34:06 (2035) [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-17 01:34:06 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-17 01:34:06 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-17 01:34:08 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/klJsnXvueV/ea_profile.json
* 2024-07-17 01:34:12 (374) [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/klJsnXvueV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-17 01:34:12 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-18 01:33:40 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-18 01:33:40 (8148) [INFO] Script is up to date.
* 2024-07-18 01:33:41 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-18 01:33:41 (2278) [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-18 01:33:41 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-18 01:33:41 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-18 01:33:41 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-18 01:33:41 (6847) [INFO] 
* 2024-07-18 01:33:47 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 29, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-18 01:33:47 (6877) [INFO] 
* 2024-07-18 01:33:47 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-18 01:33:47 (751) [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.

* 2024-07-18 01:33:47 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-18 01:33:47 (6847) [INFO] 
* 2024-07-18 01:34:15 (6877) [INFO] 
* 2024-07-18 01:34:16 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-18 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-18 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-18 01:34:16 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-18 01:34:16 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-18 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-18 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-18 01:34:16 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-18 01:34:16 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-18 01:34:21 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-18 01:34:21 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-18 01:34:21 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-18 01:34:21 (6847) [INFO] 
* 2024-07-18 01:34:21 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-18 01:34:21 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-18 01:34:21 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-18 01:34:21 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-18 01:34:21 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-18 01:34:21 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-18 01:34:21 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-18 01:34:21 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-18 01:34:21 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-18 01:34:21 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-18 01:34:21 (6860) [INFO]               : yarn
* 2024-07-18 01:34:21 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-18 01:34:21 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-18 01:34:21 (6877) [INFO] 
* 2024-07-18 01:34:28 (2035) [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-18 01:34:28 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-18 01:34:28 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-18 01:34:29 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tCKY12lxoJ/ea_profile.json
* 2024-07-18 01:34:33 (374) [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/tCKY12lxoJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-18 01:34:33 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-19 01:33:38 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-19 01:33:38 (8148) [INFO] Script is up to date.
* 2024-07-19 01:33:39 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-19 01:33:39 (2278) [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-19 01:33:39 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-19 01:33:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-19 01:33:40 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-19 01:33:40 (6847) [INFO] 
* 2024-07-19 01:33:44 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 29, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-19 01:33:44 (6877) [INFO] 
* 2024-07-19 01:33:44 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-19 01:33:44 (751) [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.

* 2024-07-19 01:33:44 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-19 01:33:44 (6847) [INFO] 
* 2024-07-19 01:34:11 (6877) [INFO] 
* 2024-07-19 01:34:13 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-19 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-19 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-19 01:34:13 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-19 01:34:13 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-19 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-19 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-19 01:34:13 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-19 01:34:13 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-19 01:34:18 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-19 01:34:18 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-19 01:34:18 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-19 01:34:18 (6847) [INFO] 
* 2024-07-19 01:34:18 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-19 01:34:19 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-19 01:34:19 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-19 01:34:19 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-19 01:34:19 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-19 01:34:19 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-19 01:34:19 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-19 01:34:19 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-19 01:34:19 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-19 01:34:19 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-19 01:34:19 (6860) [INFO]               : yarn
* 2024-07-19 01:34:19 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-19 01:34:19 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-19 01:34:19 (6877) [INFO] 
* 2024-07-19 01:34:32 (2035) [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-19 01:34:32 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-19 01:34:32 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-19 01:34:34 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tsr2jknjfe/ea_profile.json
* 2024-07-19 01:34:42 (374) [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/tsr2jknjfe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-19 01:34:42 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-20 01:34:50 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-20 01:34:50 (8148) [INFO] Script is up to date.
* 2024-07-20 01:34:52 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-20 01:34:52 (2278) [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-20 01:34:52 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-20 01:34:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-20 01:34:52 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-20 01:34:52 (6847) [INFO] 
* 2024-07-20 01:34:57 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 29, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-20 01:34:57 (6877) [INFO] 
* 2024-07-20 01:34:57 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-20 01:34:57 (751) [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.

* 2024-07-20 01:34:57 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-20 01:34:57 (6847) [INFO] 
* 2024-07-20 01:35:17 (6877) [INFO] 
* 2024-07-20 01:35:18 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-20 01:35:18 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-20 01:35:18 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-20 01:35:18 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-20 01:35:18 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-20 01:35:18 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-20 01:35:18 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-20 01:35:18 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-20 01:35:18 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-20 01:35:22 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-20 01:35:22 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-20 01:35:22 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-20 01:35:22 (6847) [INFO] 
* 2024-07-20 01:35:22 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-20 01:35:22 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-20 01:35:22 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-20 01:35:22 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-20 01:35:22 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-20 01:35:22 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-20 01:35:22 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-20 01:35:22 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-20 01:35:22 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-20 01:35:22 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-20 01:35:22 (6860) [INFO]               : yarn
* 2024-07-20 01:35:22 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-20 01:35:22 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-20 01:35:22 (6877) [INFO] 
* 2024-07-20 01:35:28 (2035) [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-20 01:35:28 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-20 01:35:28 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-20 01:35:29 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dlqF_lPSdm/ea_profile.json
* 2024-07-20 01:35:35 (374) [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/dlqF_lPSdm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-20 01:35:35 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-21 01:34:33 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-21 01:34:33 (8148) [INFO] Script is up to date.
* 2024-07-21 01:34:34 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-21 01:34:34 (2278) [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-21 01:34:34 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-21 01:34:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-21 01:34:35 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-21 01:34:35 (6847) [INFO] 
* 2024-07-21 01:34:39 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 29, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-21 01:34:39 (6877) [INFO] 
* 2024-07-21 01:34:40 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-21 01:34:40 (751) [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.

* 2024-07-21 01:34:40 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-21 01:34:40 (6847) [INFO] 
* 2024-07-21 01:34:54 (6877) [INFO] 
* 2024-07-21 01:34:56 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-21 01:34:56 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-21 01:34:56 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-21 01:34:56 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-21 01:34:56 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-21 01:34:56 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-21 01:34:56 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-21 01:34:56 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-21 01:34:56 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-21 01:35:00 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-21 01:35:00 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-21 01:35:00 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-21 01:35:00 (6847) [INFO] 
* 2024-07-21 01:35:00 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-21 01:35:01 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-21 01:35:01 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-21 01:35:01 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-21 01:35:01 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-21 01:35:01 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-21 01:35:01 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-21 01:35:01 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-21 01:35:01 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-21 01:35:01 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-21 01:35:01 (6860) [INFO]               : yarn
* 2024-07-21 01:35:01 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-21 01:35:01 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-21 01:35:01 (6877) [INFO] 
* 2024-07-21 01:35:06 (2035) [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-21 01:35:06 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-21 01:35:07 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-21 01:35:08 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/I8uDaPNvHO/ea_profile.json
* 2024-07-21 01:35:12 (374) [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/I8uDaPNvHO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-21 01:35:12 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-22 01:33:45 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-22 01:33:45 (8148) [INFO] Script is up to date.
* 2024-07-22 01:33:46 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-22 01:33:47 (2278) [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-22 01:33:47 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-22 01:33:47 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-22 01:33:47 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-22 01:33:47 (6847) [INFO] 
* 2024-07-22 01:33:57 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 29, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-22 01:33:57 (6877) [INFO] 
* 2024-07-22 01:33:57 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-22 01:33:57 (751) [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.

* 2024-07-22 01:33:57 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-22 01:33:57 (6847) [INFO] 
* 2024-07-22 01:34:09 (6877) [INFO] 
* 2024-07-22 01:34:10 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-22 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-22 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-22 01:34:10 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-22 01:34:10 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-22 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-22 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-22 01:34:10 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-22 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-22 01:34:16 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-22 01:34:16 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-22 01:34:16 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-22 01:34:16 (6847) [INFO] 
* 2024-07-22 01:34:17 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-22 01:34:17 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-22 01:34:17 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-22 01:34:17 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-22 01:34:17 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-22 01:34:17 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-22 01:34:17 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-22 01:34:17 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-22 01:34:17 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-22 01:34:17 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-22 01:34:17 (6860) [INFO]               : yarn
* 2024-07-22 01:34:17 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-22 01:34:17 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-22 01:34:17 (6877) [INFO] 
* 2024-07-22 01:34:24 (2035) [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-22 01:34:24 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-22 01:34:24 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-22 01:34:26 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TYfyp4CQcj/ea_profile.json
* 2024-07-22 01:34:33 (374) [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/TYfyp4CQcj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-22 01:34:33 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-23 01:33:37 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-23 01:33:37 (8148) [INFO] Script is up to date.
* 2024-07-23 01:33:38 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-23 01:33:39 (2278) [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-23 01:33:39 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-07-23 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-23 01:33:39 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-23 01:33:39 (6847) [INFO] 
* 2024-07-23 01:33:45 (6860) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 29, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-23 01:33:45 (6877) [INFO] 
* 2024-07-23 01:33:46 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-23 01:33:46 (751) [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.

* 2024-07-23 01:33:46 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-23 01:33:46 (6847) [INFO] 
* 2024-07-23 01:34:08 (6877) [INFO] 
* 2024-07-23 01:34:10 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-23 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-23 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-23 01:34:10 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-23 01:34:10 (2139) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-23 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-23 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-23 01:34:10 (2139) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-23 01:34:10 (2163) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-23 01:34:16 (2025) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-23 01:34:16 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-23 01:34:16 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-23 01:34:16 (6847) [INFO] 
* 2024-07-23 01:34:17 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-23 01:34:17 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-23 01:34:17 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-23 01:34:17 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-23 01:34:17 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-23 01:34:17 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-23 01:34:17 (6860) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-23 01:34:17 (6860) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-23 01:34:17 (6860) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-23 01:34:17 (6860) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-23 01:34:17 (6860) [INFO]               : yarn
* 2024-07-23 01:34:17 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-23 01:34:17 (6860) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-23 01:34:17 (6877) [INFO] 
* 2024-07-23 01:34:27 (2035) [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-23 01:34:27 (2036) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-23 01:34:27 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-23 01:34:28 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rQZ9lpDlxm/ea_profile.json
* 2024-07-23 01:34:36 (374) [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/rQZ9lpDlxm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-23 01:34:36 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-24 01:34:01 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-24 01:34:01 (8131) [INFO] Newer version of script found. Downloading.
* 2024-07-24 01:34:01 (8140) [INFO] Script update to version 49 successful.
* 2024-07-24 01:34:02 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-24 01:34:02 (2326) [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-24 01:34:02 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-24 01:34:02 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-24 01:34:02 (6908) [INFO] 
* 2024-07-24 01:34:09 (6921) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-24 01:34:09 (6938) [INFO] 
* 2024-07-24 01:34:09 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-24 01:34:09 (751) [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.

* 2024-07-24 01:34:09 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-24 01:34:09 (6908) [INFO] 
* 2024-07-24 01:34:14 (6938) [INFO] 
* 2024-07-24 01:34:15 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-24 01:34:15 (2188) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-24 01:34:15 (2188) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-24 01:34:15 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-24 01:34:15 (2164) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-24 01:34:15 (2188) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-24 01:34:15 (2188) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-24 01:34:15 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-24 01:34:15 (2188) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-24 01:34:21 (2047) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-24 01:34:21 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-24 01:34:21 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-24 01:34:21 (6908) [INFO] 
* 2024-07-24 01:34:21 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-24 01:34:21 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-24 01:34:21 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-24 01:34:21 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-24 01:34:21 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-24 01:34:21 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-24 01:34:21 (6921) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-24 01:34:21 (6921) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-24 01:34:21 (6921) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-24 01:34:21 (6921) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-24 01:34:21 (6921) [INFO]               : yarn
* 2024-07-24 01:34:21 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-24 01:34:21 (6921) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-24 01:34:21 (6938) [INFO] 
* 2024-07-24 01:34:27 (2057) [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-24 01:34:27 (2058) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-24 01:34:27 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-24 01:34:29 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NkfKFpVoY_/ea_profile.json
* 2024-07-24 01:34:34 (374) [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/NkfKFpVoY_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-24 01:34:34 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-25 01:34:02 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-25 01:34:02 (8209) [INFO] Script is up to date.
* 2024-07-25 01:34:03 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-25 01:34:03 (2326) [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-25 01:34:04 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-25 01:34:04 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-25 01:34:04 (6908) [INFO] 
* 2024-07-25 01:34:08 (6921) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-25 01:34:08 (6938) [INFO] 
* 2024-07-25 01:34:09 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-25 01:34:09 (751) [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.

* 2024-07-25 01:34:09 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-25 01:34:09 (6908) [INFO] 
* 2024-07-25 01:34:26 (6938) [INFO] 
* 2024-07-25 01:34:28 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-25 01:34:28 (2188) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-25 01:34:28 (2188) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-25 01:34:28 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-25 01:34:28 (2164) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-25 01:34:28 (2188) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-25 01:34:28 (2188) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-25 01:34:28 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-25 01:34:28 (2188) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-25 01:34:33 (2047) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-25 01:34:33 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-25 01:34:33 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-25 01:34:33 (6908) [INFO] 
* 2024-07-25 01:34:33 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-25 01:34:33 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-25 01:34:33 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-25 01:34:33 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-25 01:34:33 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-25 01:34:33 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-25 01:34:33 (6921) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-25 01:34:33 (6921) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-25 01:34:33 (6921) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-25 01:34:33 (6921) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-25 01:34:33 (6921) [INFO]               : yarn
* 2024-07-25 01:34:33 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-25 01:34:33 (6921) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-25 01:34:33 (6938) [INFO] 
* 2024-07-25 01:34:38 (2057) [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-25 01:34:38 (2058) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-25 01:34:38 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-25 01:34:40 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AanHPFsK8C/ea_profile.json
* 2024-07-25 01:34:46 (374) [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/AanHPFsK8C/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-25 01:34:46 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-26 01:33:53 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-26 01:33:54 (8209) [INFO] Script is up to date.
* 2024-07-26 01:33:54 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-26 01:33:54 (2326) [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-26 01:33:55 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-26 01:33:55 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-26 01:33:55 (6908) [INFO] 
* 2024-07-26 01:33:59 (6921) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-26 01:33:59 (6938) [INFO] 
* 2024-07-26 01:33:59 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-26 01:33:59 (751) [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.

* 2024-07-26 01:33:59 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-26 01:33:59 (6908) [INFO] 
* 2024-07-26 01:34:31 (6938) [INFO] 
* 2024-07-26 01:34:33 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-26 01:34:33 (2188) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-26 01:34:33 (2188) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-26 01:34:33 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-26 01:34:33 (2164) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-26 01:34:33 (2188) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-26 01:34:33 (2188) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-26 01:34:33 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-26 01:34:33 (2188) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-26 01:34:39 (2047) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-26 01:34:39 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-26 01:34:39 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-26 01:34:39 (6908) [INFO] 
* 2024-07-26 01:34:39 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-26 01:34:39 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-26 01:34:39 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-26 01:34:39 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-26 01:34:39 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-26 01:34:39 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-26 01:34:39 (6921) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-26 01:34:39 (6921) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-26 01:34:39 (6921) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-26 01:34:39 (6921) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-26 01:34:39 (6921) [INFO]               : yarn
* 2024-07-26 01:34:39 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-26 01:34:39 (6921) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-26 01:34:39 (6938) [INFO] 
* 2024-07-26 01:34:50 (2057) [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-26 01:34:50 (2058) [ERROR] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Peer reports it experienced an internal error."
Trying other mirror.


 One of the configured repositories failed (CentOS 7 Extended Lifecycle Support by TuxCare),
 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=centos7-els ...

     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 centos7-els
        or
            subscription-manager repos --disable=centos7-els

     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=centos7-els.skip_if_unavailable=true

failure: repodata/repomd.xml from centos7-els: [Errno 256] No more mirrors to try.
https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Peer reports it experienced an internal error."
* 2024-07-26 01:34:50 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-26 01:34:51 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B1Su9KoES_/ea_profile.json
* 2024-07-26 01:34:56 (374) [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/B1Su9KoES_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-26 01:34:56 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-30 01:33:52 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-30 01:33:57 (8209) [INFO] Script is up to date.
* 2024-07-30 01:33:58 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-30 01:33:59 (2326) [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-30 01:33:59 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-30 01:33:59 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-30 01:33:59 (6908) [INFO] 
* 2024-07-30 01:34:03 (6921) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-30 01:34:03 (6938) [INFO] 
* 2024-07-30 01:34:04 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-30 01:34:04 (751) [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.

* 2024-07-30 01:34:04 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-30 01:34:04 (6908) [INFO] 
* 2024-07-30 01:34:14 (6938) [INFO] 
* 2024-07-30 01:34:22 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-30 01:34:22 (2188) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-30 01:34:22 (2188) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-30 01:34:22 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-30 01:34:22 (2164) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-30 01:34:22 (2188) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-30 01:34:22 (2188) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-30 01:34:22 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-30 01:34:22 (2188) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-30 01:34:27 (2047) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-30 01:34:27 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-30 01:34:27 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-30 01:34:27 (6908) [INFO] 
* 2024-07-30 01:34:27 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-30 01:34:28 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-30 01:34:28 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-30 01:34:28 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-30 01:34:28 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-30 01:34:28 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-30 01:34:28 (6921) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-30 01:34:28 (6921) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-30 01:34:28 (6921) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-30 01:34:28 (6921) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-30 01:34:28 (6921) [INFO]               : yarn
* 2024-07-30 01:34:28 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-30 01:34:28 (6921) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-30 01:34:28 (6938) [INFO] 
* 2024-07-30 01:34:39 (2057) [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-30 01:34:39 (2058) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-30 01:34:39 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-30 01:34:40 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OdhqmzC9yJ/ea_profile.json
* 2024-07-30 01:34:49 (374) [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/OdhqmzC9yJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-30 01:34:49 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-31 01:34:09 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-31 01:34:09 (8209) [INFO] Script is up to date.
* 2024-07-31 01:34:10 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-07-31 01:34:10 (2326) [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-31 01:34:10 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-07-31 01:34:10 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-31 01:34:10 (6908) [INFO] 
* 2024-07-31 01:34:16 (6921) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-31 01:34:16 (6938) [INFO] 
* 2024-07-31 01:34:17 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-07-31 01:34:17 (751) [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.

* 2024-07-31 01:34:17 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-31 01:34:17 (6908) [INFO] 
* 2024-07-31 01:34:36 (6938) [INFO] 
* 2024-07-31 01:34:45 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-07-31 01:34:45 (2188) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-07-31 01:34:45 (2188) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-07-31 01:34:45 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-31 01:34:45 (2164) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-07-31 01:34:45 (2188) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-07-31 01:34:45 (2188) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-07-31 01:34:45 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-07-31 01:34:45 (2188) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-07-31 01:34:50 (2047) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-31 01:34:50 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-31 01:34:50 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-31 01:34:50 (6908) [INFO] 
* 2024-07-31 01:34:51 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-31 01:34:51 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-07-31 01:34:51 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-31 01:34:51 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-31 01:34:51 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-07-31 01:34:51 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-31 01:34:51 (6921) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-07-31 01:34:51 (6921) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-07-31 01:34:51 (6921) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-07-31 01:34:51 (6921) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-31 01:34:51 (6921) [INFO]               : yarn
* 2024-07-31 01:34:51 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-31 01:34:51 (6921) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-07-31 01:34:51 (6938) [INFO] 
* 2024-07-31 01:34:58 (2057) [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-31 01:34:58 (2058) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-07-31 01:34:58 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-31 01:35:00 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RyEF_oq7eO/ea_profile.json
* 2024-07-31 01:35:08 (374) [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/RyEF_oq7eO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-31 01:35:08 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-01 01:33:54 (8187) [INFO] Self-update of script version 49 requested.
* 2024-08-01 01:33:54 (8209) [INFO] Script is up to date.
* 2024-08-01 01:33:55 (214) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-01 01:33:55 (2326) [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-08-01 01:33:55 (214) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-01 01:33:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-01 01:33:56 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-01 01:33:56 (6908) [INFO] 
* 2024-08-01 01:34:01 (6921) [INFO] {"items": "6.12.4-1", "version": "6.12.4-1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 28, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-08-01 01:34:01 (6938) [INFO] 
* 2024-08-01 01:34:02 (744) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-01 01:34:02 (751) [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.

* 2024-08-01 01:34:02 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-08-01 01:34:02 (6908) [INFO] 
* 2024-08-01 01:34:19 (6938) [INFO] 
* 2024-08-01 01:34:20 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-01 01:34:20 (2188) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-01 01:34:20 (2188) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-01 01:34:20 (2164) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-01 01:34:20 (2164) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-01 01:34:20 (2188) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-01 01:34:20 (2188) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-01 01:34:20 (2164) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-01 01:34:20 (2188) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-01 01:34:26 (2047) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-01 01:34:26 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-01 01:34:26 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-08-01 01:34:26 (6908) [INFO] 
* 2024-08-01 01:34:27 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-01 01:34:27 (6921) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 722204.
* 2024-08-01 01:34:27 (6921) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-01 01:34:27 (6921) [INFO]   The other application is: yum
* 2024-08-01 01:34:27 (6921) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-08-01 01:34:27 (6921) [INFO]     Started: Thu Aug  1 01:34:12 2024 - 00:15 ago
* 2024-08-01 01:34:27 (6921) [INFO]     State  : Sleeping, pid: 722204
* 2024-08-01 01:34:29 (6921) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-01 01:34:29 (6921) [INFO]   The other application is: yum
* 2024-08-01 01:34:29 (6921) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-08-01 01:34:29 (6921) [INFO]     Started: Thu Aug  1 01:34:12 2024 - 00:17 ago
* 2024-08-01 01:34:29 (6921) [INFO]     State  : Sleeping, pid: 722204
* 2024-08-01 01:34:31 (6921) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-01 01:34:31 (6921) [INFO]   The other application is: yum
* 2024-08-01 01:34:31 (6921) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-08-01 01:34:31 (6921) [INFO]     Started: Thu Aug  1 01:34:12 2024 - 00:19 ago
* 2024-08-01 01:34:31 (6921) [INFO]     State  : Sleeping, pid: 722204
* 2024-08-01 01:34:33 (6921) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-01 01:34:33 (6921) [INFO]   The other application is: yum
* 2024-08-01 01:34:33 (6921) [INFO]     Memory :  40 M RSS (334 MB VSZ)
* 2024-08-01 01:34:33 (6921) [INFO]     Started: Thu Aug  1 01:34:12 2024 - 00:21 ago
* 2024-08-01 01:34:33 (6921) [INFO]     State  : Running, pid: 722204
* 2024-08-01 01:34:35 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-01 01:34:35 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-01 01:34:35 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-01 01:34:35 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-01 01:34:35 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-01 01:34:35 (6921) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-01 01:34:35 (6921) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-01 01:34:35 (6921) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-01 01:34:35 (6921) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-01 01:34:35 (6921) [INFO]               : yarn
* 2024-08-01 01:34:35 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-08-01 01:34:35 (6921) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-01 01:34:35 (6938) [INFO] 
* 2024-08-01 01:34:41 (2057) [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-08-01 01:34:41 (2058) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-01 01:34:42 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-01 01:34:43 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dWdXjeSxFN/ea_profile.json
* 2024-08-01 01:34:50 (374) [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/dWdXjeSxFN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-08-01 01:34:50 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-02 01:34:03 (8187) [INFO] Self-update of script version 49 requested.
* 2024-08-02 01:34:03 (8192) [INFO] Newer version of script found. Downloading.
* 2024-08-02 01:34:04 (8201) [INFO] Script update to version 50 successful.
* 2024-08-02 01:34:05 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-02 01:34:05 (2338) [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-08-02 01:34:05 (226) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-02 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-02 01:34:08 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-02 01:34:08 (7164) [INFO] 
* 2024-08-02 01:34:14 (756) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-02 01:34:14 (763) [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.

* 2024-08-02 01:34:14 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-02 01:34:14 (7164) [INFO] 
* 2024-08-02 01:34:39 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-02 01:34:39 (2200) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-02 01:34:39 (2200) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-02 01:34:39 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-02 01:34:39 (2176) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-02 01:34:39 (2200) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-02 01:34:39 (2200) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-02 01:34:39 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-02 01:34:39 (2200) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-02 01:34:45 (2059) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-02 01:34:45 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-02 01:34:45 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-02 01:34:45 (7164) [INFO] 
* 2024-08-02 01:34:45 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-02 01:34:45 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-02 01:34:45 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-02 01:34:45 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-02 01:34:45 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-02 01:34:45 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-02 01:34:45 (7177) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-02 01:34:45 (7177) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-02 01:34:45 (7177) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-02 01:34:45 (7177) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-02 01:34:45 (7177) [INFO]               : yarn
* 2024-08-02 01:34:45 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-02 01:34:45 (7177) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-02 01:34:45 (7194) [INFO] 
* 2024-08-02 01:34:51 (2069) [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-08-02 01:34:51 (2070) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-02 01:34:51 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-02 01:34:52 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oyBC1RLSoZ/ea_profile.json
* 2024-08-02 01:34:58 (386) [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/oyBC1RLSoZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-02 01:34:59 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-03 01:35:51 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-03 01:35:51 (8496) [INFO] Script is up to date.
* 2024-08-03 01:35:52 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-03 01:35:52 (2338) [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-08-03 01:35:52 (226) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-03 01:35:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-03 01:35:53 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-03 01:35:53 (7164) [INFO] 
* 2024-08-03 01:35:59 (756) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-03 01:35:59 (763) [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.

* 2024-08-03 01:35:59 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-03 01:35:59 (7164) [INFO] 
* 2024-08-03 01:36:15 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-03 01:36:15 (2200) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-03 01:36:15 (2200) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-03 01:36:15 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-03 01:36:15 (2176) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-03 01:36:15 (2200) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-03 01:36:15 (2200) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-03 01:36:15 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-03 01:36:15 (2200) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-03 01:36:21 (2059) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-03 01:36:21 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-03 01:36:21 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-03 01:36:21 (7164) [INFO] 
* 2024-08-03 01:36:21 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-03 01:36:21 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-03 01:36:21 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-03 01:36:21 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-03 01:36:21 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-03 01:36:21 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-03 01:36:22 (7177) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-03 01:36:22 (7177) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-03 01:36:22 (7177) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-03 01:36:22 (7177) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-03 01:36:22 (7177) [INFO]               : yarn
* 2024-08-03 01:36:22 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-03 01:36:22 (7177) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-03 01:36:22 (7194) [INFO] 
* 2024-08-03 01:36:28 (2069) [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-08-03 01:36:28 (2070) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-03 01:36:28 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-03 01:36:29 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4orEWlE6XV/ea_profile.json
* 2024-08-03 01:36:35 (386) [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/4orEWlE6XV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-03 01:36:35 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-04 01:36:15 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-04 01:36:15 (8496) [INFO] Script is up to date.
* 2024-08-04 01:36:16 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-04 01:36:16 (2338) [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-08-04 01:36:16 (226) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-04 01:36:17 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-04 01:36:17 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-04 01:36:17 (7164) [INFO] 
* 2024-08-04 01:36:25 (756) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-04 01:36:25 (763) [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.

* 2024-08-04 01:36:25 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-04 01:36:25 (7164) [INFO] 
* 2024-08-04 01:36:47 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-04 01:36:48 (2200) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-04 01:36:48 (2200) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-04 01:36:48 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-04 01:36:48 (2176) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-04 01:36:48 (2200) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-04 01:36:48 (2200) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-04 01:36:48 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-04 01:36:48 (2200) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-04 01:36:53 (2059) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-04 01:36:53 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-04 01:36:53 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-04 01:36:53 (7164) [INFO] 
* 2024-08-04 01:36:53 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-04 01:36:54 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-04 01:36:54 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-04 01:36:54 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-04 01:36:54 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-04 01:36:54 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-04 01:36:54 (7177) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-04 01:36:54 (7177) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-04 01:36:54 (7177) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-04 01:36:54 (7177) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-04 01:36:54 (7177) [INFO]               : yarn
* 2024-08-04 01:36:54 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-04 01:36:54 (7177) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-04 01:36:54 (7194) [INFO] 
* 2024-08-04 01:37:00 (2069) [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-08-04 01:37:00 (2070) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-04 01:37:00 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-04 01:37:01 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Dt56pS2ikd/ea_profile.json
* 2024-08-04 01:37:10 (386) [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/Dt56pS2ikd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-04 01:37:10 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-05 01:33:48 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-05 01:33:48 (8496) [INFO] Script is up to date.
* 2024-08-05 01:33:49 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-05 01:33:49 (2338) [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-08-05 01:33:49 (226) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-05 01:33:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-05 01:33:49 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-05 01:33:49 (7164) [INFO] 
* 2024-08-05 01:33:54 (756) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-05 01:33:54 (763) [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.

* 2024-08-05 01:33:54 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-05 01:33:54 (7164) [INFO] 
* 2024-08-05 01:34:21 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-05 01:34:21 (2200) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-05 01:34:21 (2200) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-05 01:34:21 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-05 01:34:21 (2176) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-05 01:34:21 (2200) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-05 01:34:21 (2200) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-05 01:34:21 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-05 01:34:21 (2200) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-05 01:34:28 (2059) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-05 01:34:28 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-05 01:34:28 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-05 01:34:28 (7164) [INFO] 
* 2024-08-05 01:34:28 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-05 01:34:28 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-05 01:34:28 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-05 01:34:28 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-05 01:34:28 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-05 01:34:28 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-05 01:34:28 (7177) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-05 01:34:28 (7177) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-05 01:34:28 (7177) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-05 01:34:28 (7177) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-05 01:34:28 (7177) [INFO]               : yarn
* 2024-08-05 01:34:28 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-05 01:34:28 (7177) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-05 01:34:28 (7194) [INFO] 
* 2024-08-05 01:34:35 (2069) [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-08-05 01:34:35 (2070) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-05 01:34:35 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-05 01:34:36 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8__UXQonjP/ea_profile.json
* 2024-08-05 01:34:43 (386) [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/8__UXQonjP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-05 01:34:43 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-06 01:33:43 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-06 01:33:43 (8496) [INFO] Script is up to date.
* 2024-08-06 01:33:44 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-06 01:33:44 (2338) [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-08-06 01:33:44 (226) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-06 01:33:44 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-06 01:33:44 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-06 01:33:44 (7164) [INFO] 
* 2024-08-06 01:33:52 (756) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-06 01:33:52 (763) [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.

* 2024-08-06 01:33:52 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-06 01:33:52 (7164) [INFO] 
* 2024-08-06 01:34:07 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-06 01:34:07 (2200) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-06 01:34:07 (2200) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-06 01:34:07 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-06 01:34:07 (2176) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-06 01:34:07 (2200) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-06 01:34:07 (2200) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-06 01:34:07 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-06 01:34:07 (2200) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-06 01:34:16 (2059) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-06 01:34:16 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-06 01:34:16 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-06 01:34:16 (7164) [INFO] 
* 2024-08-06 01:34:16 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-06 01:34:16 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-06 01:34:16 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-06 01:34:16 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-06 01:34:16 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-06 01:34:16 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-06 01:34:16 (7177) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-06 01:34:16 (7177) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-06 01:34:16 (7177) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-06 01:34:16 (7177) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-06 01:34:16 (7177) [INFO]               : yarn
* 2024-08-06 01:34:16 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-06 01:34:16 (7177) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-06 01:34:16 (7194) [INFO] 
* 2024-08-06 01:34:31 (2069) [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-08-06 01:34:31 (2070) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 297537.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Tue Aug  6 01:33:55 2024 - 00:22 ago
    State  : Sleeping, pid: 297537
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Tue Aug  6 01:33:55 2024 - 00:24 ago
    State  : Sleeping, pid: 297537
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Tue Aug  6 01:33:55 2024 - 00:26 ago
    State  : Sleeping, pid: 297537
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Tue Aug  6 01:33:55 2024 - 00:28 ago
    State  : Sleeping, pid: 297537
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-06 01:34:31 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-06 01:34:33 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Z3rQ8CrX3J/ea_profile.json
* 2024-08-06 01:34:40 (386) [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/Z3rQ8CrX3J/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-06 01:34:40 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-07 01:34:55 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-07 01:34:55 (8496) [INFO] Script is up to date.
* 2024-08-07 01:34:56 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-07 01:34:56 (2338) [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-08-07 01:34:56 (226) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-07 01:34:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-07 01:34:56 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-07 01:34:56 (7164) [INFO] 
* 2024-08-07 01:35:01 (756) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-07 01:35:01 (763) [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.

* 2024-08-07 01:35:02 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-07 01:35:02 (7164) [INFO] 
* 2024-08-07 01:35:53 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-07 01:35:53 (2200) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-07 01:35:53 (2200) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-07 01:35:53 (2176) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-07 01:35:53 (2176) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-07 01:35:53 (2200) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-07 01:35:53 (2200) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-07 01:35:53 (2176) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-07 01:35:53 (2200) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-07 01:36:00 (2059) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-07 01:36:00 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-07 01:36:00 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-07 01:36:00 (7164) [INFO] 
* 2024-08-07 01:36:00 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-07 01:36:00 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-07 01:36:00 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-07 01:36:00 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-07 01:36:00 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-07 01:36:00 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-07 01:36:00 (7177) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-07 01:36:00 (7177) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-07 01:36:00 (7177) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-07 01:36:00 (7177) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-07 01:36:00 (7177) [INFO]               : yarn
* 2024-08-07 01:36:00 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-07 01:36:00 (7177) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-07 01:36:00 (7194) [INFO] 
* 2024-08-07 01:36:08 (2069) [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-08-07 01:36:08 (2070) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-07 01:36:08 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-07 01:36:09 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RD9l5ByUQD/ea_profile.json
* 2024-08-07 01:36:15 (386) [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/RD9l5ByUQD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-07 01:36:15 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-08 01:33:40 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-08 01:33:40 (8479) [INFO] Newer version of script found. Downloading.
* 2024-08-08 01:33:40 (8488) [INFO] Script update to version 51 successful.
* 2024-08-08 01:33:41 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-08 01:33:42 (2308) [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-08-08 01:33:42 (226) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-08-08 01:33:42 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-08 01:33:42 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-08 01:33:42 (7324) [INFO] 
* 2024-08-08 01:33:47 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-08 01:33:47 (746) [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.

* 2024-08-08 01:33:47 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-08 01:33:47 (7324) [INFO] 
* 2024-08-08 01:33:56 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-08 01:33:56 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-08 01:33:56 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-08 01:33:56 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-08 01:33:56 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-08 01:33:56 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-08 01:33:56 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-08 01:33:56 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-08 01:33:56 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-08 01:34:00 (2029) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 1040742.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Thu Aug  8 01:33:51 2024 - 00:05 ago
    State  : Sleeping, pid: 1040742


 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

Insufficient space in download directory /var/cache/yum/x86_64/7/mongodb-org-4.0
    * free   0 
    * needed 100 k
* 2024-08-08 01:34:00 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-08 01:34:00 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-08 01:34:00 (7324) [INFO] 
* 2024-08-08 01:34:01 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-08 01:34:01 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-08 01:34:01 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-08 01:34:01 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-08 01:34:01 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-08 01:34:01 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-08 01:34:01 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-08 01:34:01 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-08 01:34:01 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-08 01:34:01 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-08 01:34:01 (7337) [INFO]               : yarn
* 2024-08-08 01:34:01 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-08 01:34:01 (7337) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-08-08 01:34:01 (7354) [INFO] 
* 2024-08-08 01:34:05 (2039) [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-08-08 01:34:05 (2040) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-08-08 01:34:05 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-08 01:34:07 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bohfqc9SPN/ea_profile.json
* 2024-08-08 01:34:08 (386) [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/bohfqc9SPN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-08 01:34:08 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-09 01:33:54 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-09 01:33:54 (8664) [INFO] Script is up to date.
* 2024-08-09 01:33:55 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-09 01:33:55 (2308) [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-08-09 01:33:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-09 01:33:56 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-09 01:33:56 (7324) [INFO] 
* 2024-08-09 01:34:03 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-09 01:34:03 (746) [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.

* 2024-08-09 01:34:03 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-09 01:34:03 (7324) [INFO] 
* 2024-08-09 01:34:20 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-09 01:34:20 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-09 01:34:20 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-09 01:34:20 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-09 01:34:20 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-09 01:34:20 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-09 01:34:20 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-09 01:34:20 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-09 01:34:20 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-09 01:34:26 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-09 01:34:26 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-09 01:34:26 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-09 01:34:26 (7324) [INFO] 
* 2024-08-09 01:34:26 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-09 01:34:26 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-09 01:34:26 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-09 01:34:26 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-09 01:34:26 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-09 01:34:26 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-09 01:34:26 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-09 01:34:26 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-09 01:34:26 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-09 01:34:26 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-09 01:34:26 (7337) [INFO]               : yarn
* 2024-08-09 01:34:26 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-09 01:34:26 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-09 01:34:26 (7354) [INFO] 
* 2024-08-09 01:34:34 (2039) [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-08-09 01:34:34 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-09 01:34:34 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-09 01:34:36 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PodSqktj73/ea_profile.json
* 2024-08-09 01:34:43 (386) [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/PodSqktj73/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-09 01:34:43 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-10 01:35:37 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-10 01:35:37 (8664) [INFO] Script is up to date.
* 2024-08-10 01:35:38 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-10 01:35:38 (2308) [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-08-10 01:35:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-10 01:35:38 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-10 01:35:38 (7324) [INFO] 
* 2024-08-10 01:35:44 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-10 01:35:44 (746) [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.

* 2024-08-10 01:35:44 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-10 01:35:44 (7324) [INFO] 
* 2024-08-10 01:36:09 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-10 01:36:09 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-10 01:36:09 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-10 01:36:09 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-10 01:36:09 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-10 01:36:09 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-10 01:36:09 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-10 01:36:09 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-10 01:36:09 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-10 01:36:14 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-10 01:36:14 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-10 01:36:14 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-10 01:36:14 (7324) [INFO] 
* 2024-08-10 01:36:15 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-10 01:36:15 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-10 01:36:15 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-10 01:36:15 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-10 01:36:15 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-10 01:36:15 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-10 01:36:15 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-10 01:36:15 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-10 01:36:15 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-10 01:36:15 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-10 01:36:15 (7337) [INFO]               : yarn
* 2024-08-10 01:36:15 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-10 01:36:15 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-10 01:36:15 (7354) [INFO] 
* 2024-08-10 01:36:21 (2039) [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-08-10 01:36:21 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-10 01:36:22 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-10 01:36:23 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_4FJ2yPwYv/ea_profile.json
* 2024-08-10 01:36:29 (386) [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/_4FJ2yPwYv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-10 01:36:29 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-11 01:35:35 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-11 01:35:35 (8664) [INFO] Script is up to date.
* 2024-08-11 01:35:36 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-11 01:35:36 (2308) [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-08-11 01:35:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-11 01:35:36 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-11 01:35:36 (7324) [INFO] 
* 2024-08-11 01:35:52 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-11 01:35:52 (746) [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.

* 2024-08-11 01:35:52 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-11 01:35:52 (7324) [INFO] 
* 2024-08-11 01:36:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-11 01:36:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-11 01:36:17 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-11 01:36:17 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-11 01:36:17 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-11 01:36:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-11 01:36:17 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-11 01:36:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-11 01:36:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-11 01:36:26 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-11 01:36:26 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-11 01:36:26 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-11 01:36:26 (7324) [INFO] 
* 2024-08-11 01:36:26 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-11 01:36:26 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-11 01:36:26 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-11 01:36:26 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-11 01:36:26 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-11 01:36:26 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-11 01:36:26 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-11 01:36:26 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-11 01:36:26 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-11 01:36:26 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-11 01:36:26 (7337) [INFO]               : yarn
* 2024-08-11 01:36:26 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-11 01:36:26 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-11 01:36:26 (7354) [INFO] 
* 2024-08-11 01:36:37 (2039) [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-08-11 01:36:37 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-11 01:36:37 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-11 01:36:39 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YYJo8rLLON/ea_profile.json
* 2024-08-11 01:36:49 (386) [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/YYJo8rLLON/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-11 01:36:49 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-12 01:33:37 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-12 01:33:37 (8664) [INFO] Script is up to date.
* 2024-08-12 01:33:38 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-12 01:33:39 (2308) [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-08-12 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-12 01:33:39 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-12 01:33:39 (7324) [INFO] 
* 2024-08-12 01:33:43 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-12 01:33:43 (746) [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.

* 2024-08-12 01:33:43 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-12 01:33:43 (7324) [INFO] 
* 2024-08-12 01:34:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-12 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-12 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-12 01:34:17 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-12 01:34:17 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-12 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-12 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-12 01:34:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-12 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-12 01:34:22 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-12 01:34:22 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-12 01:34:22 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-12 01:34:22 (7324) [INFO] 
* 2024-08-12 01:34:23 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-12 01:34:23 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-12 01:34:23 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-12 01:34:23 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-12 01:34:23 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-12 01:34:23 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-12 01:34:23 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-12 01:34:23 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-12 01:34:23 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-12 01:34:23 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-12 01:34:23 (7337) [INFO]               : yarn
* 2024-08-12 01:34:23 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-12 01:34:23 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-12 01:34:23 (7354) [INFO] 
* 2024-08-12 01:34:29 (2039) [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-08-12 01:34:29 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-12 01:34:29 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-12 01:34:30 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4_BkT_TDMp/ea_profile.json
* 2024-08-12 01:34:37 (386) [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/4_BkT_TDMp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-12 01:34:37 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-13 01:33:45 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-13 01:33:46 (8664) [INFO] Script is up to date.
* 2024-08-13 01:33:47 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-13 01:33:47 (2308) [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-08-13 01:33:47 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-13 01:33:47 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-13 01:33:47 (7324) [INFO] 
* 2024-08-13 01:33:53 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-13 01:33:53 (746) [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.

* 2024-08-13 01:33:53 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-13 01:33:53 (7324) [INFO] 
* 2024-08-13 01:34:19 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-13 01:34:19 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-13 01:34:19 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-13 01:34:19 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-13 01:34:19 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-13 01:34:19 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-13 01:34:19 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-13 01:34:19 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-13 01:34:19 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-13 01:34:26 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-13 01:34:26 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-13 01:34:26 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-13 01:34:26 (7324) [INFO] 
* 2024-08-13 01:34:26 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-13 01:34:26 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-13 01:34:26 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-13 01:34:26 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-13 01:34:26 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-13 01:34:26 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-13 01:34:26 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-13 01:34:26 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-13 01:34:26 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-13 01:34:26 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-13 01:34:26 (7337) [INFO]               : yarn
* 2024-08-13 01:34:26 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-13 01:34:26 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-13 01:34:26 (7354) [INFO] 
* 2024-08-13 01:34:33 (2039) [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-08-13 01:34:33 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-13 01:34:33 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-13 01:34:35 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/44DHQxEhMd/ea_profile.json
* 2024-08-13 01:34:42 (386) [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/44DHQxEhMd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-13 01:34:42 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-14 01:34:45 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-14 01:34:45 (8664) [INFO] Script is up to date.
* 2024-08-14 01:34:46 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-14 01:34:47 (2308) [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-08-14 01:34:47 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-14 01:34:47 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-14 01:34:47 (7324) [INFO] 
* 2024-08-14 01:34:52 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-14 01:34:52 (746) [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.

* 2024-08-14 01:34:52 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-14 01:34:52 (7324) [INFO] 
* 2024-08-14 01:35:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-14 01:35:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-14 01:35:17 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-14 01:35:17 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-14 01:35:17 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-14 01:35:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-14 01:35:17 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-14 01:35:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-14 01:35:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-14 01:35:23 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-14 01:35:23 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-14 01:35:23 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-14 01:35:23 (7324) [INFO] 
* 2024-08-14 01:35:23 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-14 01:35:23 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-14 01:35:23 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-14 01:35:23 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-14 01:35:23 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-14 01:35:23 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-14 01:35:23 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-14 01:35:23 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-14 01:35:23 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-14 01:35:23 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-14 01:35:23 (7337) [INFO]               : yarn
* 2024-08-14 01:35:23 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-14 01:35:23 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-14 01:35:23 (7354) [INFO] 
* 2024-08-14 01:36:59 (2039) [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-08-14 01:36:59 (2040) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 493871.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:17 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:19 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:21 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:23 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:25 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:27 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:29 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:31 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:33 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:35 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:37 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:39 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:41 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:43 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:45 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:47 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:49 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:51 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:53 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:55 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:57 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 00:59 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 01:01 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 01:03 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 01:05 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 01:07 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 01:09 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 01:11 ago
    State  : Sleeping, pid: 493871
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Wed Aug 14 01:35:06 2024 - 01:13 ago
    State  : Sleeping, pid: 493871
https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-14 01:36:59 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-14 01:37:07 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aoFrS1LWi9/ea_profile.json
* 2024-08-14 01:38:40 (386) [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/aoFrS1LWi9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-14 01:38:40 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-15 01:33:39 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-15 01:33:39 (8664) [INFO] Script is up to date.
* 2024-08-15 01:33:40 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-15 01:33:41 (2308) [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-08-15 01:33:41 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-15 01:33:41 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-15 01:33:41 (7324) [INFO] 
* 2024-08-15 01:33:46 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-15 01:33:46 (746) [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.

* 2024-08-15 01:33:46 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-15 01:33:46 (7324) [INFO] 
* 2024-08-15 01:34:09 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-15 01:34:09 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-15 01:34:09 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-15 01:34:09 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-15 01:34:09 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-15 01:34:09 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-15 01:34:09 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-15 01:34:09 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-15 01:34:09 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-15 01:34:27 (2029) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 924501.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  37 M RSS (331 MB VSZ)
    Started: Thu Aug 15 01:33:58 2024 - 00:12 ago
    State  : Sleeping, pid: 924501
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Thu Aug 15 01:33:58 2024 - 00:14 ago
    State  : Sleeping, pid: 924501
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Thu Aug 15 01:33:58 2024 - 00:16 ago
    State  : Sleeping, pid: 924501
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (333 MB VSZ)
    Started: Thu Aug 15 01:33:58 2024 - 00:18 ago
    State  : Sleeping, pid: 924501
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (334 MB VSZ)
    Started: Thu Aug 15 01:33:58 2024 - 00:20 ago
    State  : Running, pid: 924501
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-15 01:34:27 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-15 01:34:27 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-15 01:34:27 (7324) [INFO] 
* 2024-08-15 01:34:27 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-15 01:34:28 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-15 01:34:28 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-15 01:34:28 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-15 01:34:28 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-15 01:34:28 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-15 01:34:28 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-15 01:34:28 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-15 01:34:28 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-15 01:34:28 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-15 01:34:28 (7337) [INFO]               : yarn
* 2024-08-15 01:34:28 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-15 01:34:28 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-15 01:34:28 (7354) [INFO] 
* 2024-08-15 01:34:37 (2039) [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-08-15 01:34:37 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-15 01:34:37 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-15 01:34:38 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Jp7fMMcSxA/ea_profile.json
* 2024-08-15 01:34:49 (386) [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/Jp7fMMcSxA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-15 01:34:49 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-16 01:35:05 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-16 01:35:06 (8664) [INFO] Script is up to date.
* 2024-08-16 01:35:07 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-16 01:35:07 (2308) [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-08-16 01:35:07 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-16 01:35:07 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-16 01:35:07 (7324) [INFO] 
* 2024-08-16 01:35:15 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-16 01:35:15 (746) [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.

* 2024-08-16 01:35:15 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-16 01:35:15 (7324) [INFO] 
* 2024-08-16 01:35:35 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-16 01:35:35 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-16 01:35:35 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-16 01:35:35 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-16 01:35:35 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-16 01:35:35 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-16 01:35:35 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-16 01:35:35 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-16 01:35:35 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-16 01:35:41 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-16 01:35:41 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-16 01:35:41 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-16 01:35:41 (7324) [INFO] 
* 2024-08-16 01:35:41 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-16 01:35:42 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-16 01:35:42 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-16 01:35:42 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-16 01:35:42 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-16 01:35:42 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-16 01:35:42 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-16 01:35:42 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-16 01:35:42 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-16 01:35:42 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-16 01:35:42 (7337) [INFO]               : yarn
* 2024-08-16 01:35:42 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-16 01:35:42 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-16 01:35:42 (7354) [INFO] 
* 2024-08-16 01:35:48 (2039) [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-08-16 01:35:48 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-16 01:35:48 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-16 01:35:50 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CvEtwi27qc/ea_profile.json
* 2024-08-16 01:35:55 (386) [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/CvEtwi27qc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-16 01:35:55 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-17 01:35:18 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-17 01:35:18 (8664) [INFO] Script is up to date.
* 2024-08-17 01:35:19 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-17 01:35:19 (2308) [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-08-17 01:35:19 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-17 01:35:19 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-17 01:35:19 (7324) [INFO] 
* 2024-08-17 01:35:26 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-17 01:35:26 (746) [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.

* 2024-08-17 01:35:26 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-17 01:35:26 (7324) [INFO] 
* 2024-08-17 01:35:39 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-17 01:35:39 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-17 01:35:39 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-17 01:35:39 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-17 01:35:39 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-17 01:35:39 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-17 01:35:39 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-17 01:35:39 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-17 01:35:39 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-17 01:36:17 (2029) [WARN] Initial run of "yum makecache" failed: https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-17 01:36:17 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-17 01:36:17 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-17 01:36:17 (7324) [INFO] 
* 2024-08-17 01:36:17 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-17 01:36:17 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-17 01:36:17 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-17 01:36:17 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-17 01:36:17 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-17 01:36:17 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-17 01:36:17 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-17 01:36:17 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-17 01:36:17 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-17 01:36:17 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-17 01:36:17 (7337) [INFO]               : yarn
* 2024-08-17 01:36:17 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-17 01:36:17 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-17 01:36:17 (7354) [INFO] 
* 2024-08-17 01:36:28 (2039) [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-08-17 01:36:28 (2040) [ERROR] https://cdn.centos.no/remi/enterprise/7/php72/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/php73/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
https://cdn.centos.no/remi/enterprise/7/safe/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 599 - The requested URL returned error: 599 invalid origin configuration
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-17 01:36:29 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-17 01:36:30 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_OYGGLsdPZ/ea_profile.json
* 2024-08-17 01:36:35 (386) [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/_OYGGLsdPZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-17 01:36:35 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-18 01:35:54 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-18 01:35:54 (8664) [INFO] Script is up to date.
* 2024-08-18 01:35:55 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-18 01:35:55 (2308) [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-08-18 01:35:55 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-18 01:35:55 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-18 01:35:55 (7324) [INFO] 
* 2024-08-18 01:35:59 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-18 01:35:59 (746) [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.

* 2024-08-18 01:35:59 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-18 01:35:59 (7324) [INFO] 
* 2024-08-18 01:36:18 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-18 01:36:18 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-18 01:36:18 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-18 01:36:18 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-18 01:36:18 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-18 01:36:18 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-18 01:36:18 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-18 01:36:18 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-18 01:36:18 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-18 01:36:24 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-18 01:36:24 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-18 01:36:24 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-18 01:36:24 (7324) [INFO] 
* 2024-08-18 01:36:25 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-18 01:36:25 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-18 01:36:25 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-18 01:36:25 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-18 01:36:25 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-18 01:36:25 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-18 01:36:25 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-18 01:36:25 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-18 01:36:25 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-18 01:36:25 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-18 01:36:25 (7337) [INFO]               : yarn
* 2024-08-18 01:36:25 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-18 01:36:25 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-18 01:36:25 (7354) [INFO] 
* 2024-08-18 01:36:33 (2039) [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-08-18 01:36:33 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-18 01:36:33 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-18 01:36:34 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_nlzRGHnZq/ea_profile.json
* 2024-08-18 01:36:39 (386) [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/_nlzRGHnZq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-18 01:36:39 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-19 01:33:44 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-19 01:33:46 (8664) [INFO] Script is up to date.
* 2024-08-19 01:33:47 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-19 01:33:47 (2308) [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-08-19 01:33:47 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-19 01:33:47 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-19 01:33:47 (7324) [INFO] 
* 2024-08-19 01:33:53 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-19 01:33:53 (746) [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.

* 2024-08-19 01:33:53 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-19 01:33:53 (7324) [INFO] 
* 2024-08-19 01:34:10 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-19 01:34:10 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-19 01:34:10 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-19 01:34:10 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-19 01:34:10 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-19 01:34:10 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-19 01:34:10 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-19 01:34:10 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-19 01:34:10 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-19 01:34:25 (2029) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 556747.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Mon Aug 19 01:33:59 2024 - 00:11 ago
    State  : Sleeping, pid: 556747
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Mon Aug 19 01:33:59 2024 - 00:13 ago
    State  : Sleeping, pid: 556747
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (332 MB VSZ)
    Started: Mon Aug 19 01:33:59 2024 - 00:15 ago
    State  : Sleeping, pid: 556747
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Mon Aug 19 01:33:59 2024 - 00:17 ago
    State  : Sleeping, pid: 556747
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-19 01:34:25 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-19 01:34:25 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-19 01:34:25 (7324) [INFO] 
* 2024-08-19 01:34:25 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-19 01:34:25 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-19 01:34:25 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-19 01:34:25 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-19 01:34:25 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-19 01:34:25 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-19 01:34:25 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-19 01:34:25 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-19 01:34:25 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-19 01:34:25 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-19 01:34:25 (7337) [INFO]               : yarn
* 2024-08-19 01:34:25 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-19 01:34:25 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-19 01:34:26 (7354) [INFO] 
* 2024-08-19 01:34:33 (2039) [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-08-19 01:34:33 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-19 01:34:33 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-19 01:34:34 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fPyc0VYPqL/ea_profile.json
* 2024-08-19 01:34:42 (386) [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/fPyc0VYPqL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-19 01:34:42 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-20 01:33:55 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-20 01:33:55 (8664) [INFO] Script is up to date.
* 2024-08-20 01:33:56 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-20 01:33:56 (2308) [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-08-20 01:33:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-20 01:33:56 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-20 01:33:56 (7324) [INFO] 
* 2024-08-20 01:34:04 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-20 01:34:04 (746) [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.

* 2024-08-20 01:34:04 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-20 01:34:04 (7324) [INFO] 
* 2024-08-20 01:34:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-20 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-20 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-20 01:34:17 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-20 01:34:17 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-20 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-20 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-20 01:34:17 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-20 01:34:17 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-20 01:34:23 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-20 01:34:23 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-20 01:34:23 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-20 01:34:23 (7324) [INFO] 
* 2024-08-20 01:34:23 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-20 01:34:23 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-20 01:34:23 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-20 01:34:23 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-20 01:34:23 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-20 01:34:23 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-20 01:34:23 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-20 01:34:23 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-20 01:34:23 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-20 01:34:23 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-20 01:34:23 (7337) [INFO]               : yarn
* 2024-08-20 01:34:23 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-20 01:34:23 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-20 01:34:23 (7354) [INFO] 
* 2024-08-20 01:34:31 (2039) [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-08-20 01:34:31 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-20 01:34:31 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-20 01:34:33 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hEaXQ15LH5/ea_profile.json
* 2024-08-20 01:34:40 (386) [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/hEaXQ15LH5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-20 01:34:40 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-21 01:33:54 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-21 01:33:54 (8664) [INFO] Script is up to date.
* 2024-08-21 01:33:55 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-21 01:33:56 (2308) [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-08-21 01:33:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-21 01:33:56 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-21 01:33:56 (7324) [INFO] 
* 2024-08-21 01:34:04 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-21 01:34:04 (746) [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.

* 2024-08-21 01:34:04 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-21 01:34:04 (7324) [INFO] 
* 2024-08-21 01:34:23 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-21 01:34:23 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-21 01:34:23 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-21 01:34:23 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-21 01:34:23 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-21 01:34:23 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-21 01:34:23 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-21 01:34:23 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-21 01:34:23 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-21 01:34:30 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-21 01:34:30 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-21 01:34:30 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-21 01:34:30 (7324) [INFO] 
* 2024-08-21 01:34:30 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-21 01:34:30 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-21 01:34:30 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-21 01:34:30 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-21 01:34:30 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-21 01:34:30 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-21 01:34:30 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-21 01:34:30 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-21 01:34:30 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-21 01:34:30 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-21 01:34:30 (7337) [INFO]               : yarn
* 2024-08-21 01:34:30 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-21 01:34:30 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-21 01:34:30 (7354) [INFO] 
* 2024-08-21 01:34:37 (2039) [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-08-21 01:34:37 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-21 01:34:37 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-21 01:34:38 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b7bS7Ut0lz/ea_profile.json
* 2024-08-21 01:34:45 (386) [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/b7bS7Ut0lz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-21 01:34:45 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-22 01:33:51 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-22 01:33:51 (8664) [INFO] Script is up to date.
* 2024-08-22 01:33:52 (226) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-22 01:33:52 (2308) [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-08-22 01:33:53 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-22 01:33:53 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-22 01:33:53 (7324) [INFO] 
* 2024-08-22 01:33:58 (739) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-22 01:33:58 (746) [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.

* 2024-08-22 01:33:58 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-22 01:33:58 (7324) [INFO] 
* 2024-08-22 01:34:29 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-22 01:34:29 (2170) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-22 01:34:29 (2170) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-22 01:34:29 (2146) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-22 01:34:29 (2146) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-22 01:34:29 (2170) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-22 01:34:29 (2170) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-22 01:34:29 (2146) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-22 01:34:29 (2170) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-22 01:34:38 (2029) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-22 01:34:38 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-22 01:34:38 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-22 01:34:38 (7324) [INFO] 
* 2024-08-22 01:34:39 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-22 01:34:39 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-22 01:34:39 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-22 01:34:39 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-22 01:34:39 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-22 01:34:39 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-22 01:34:39 (7337) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-22 01:34:39 (7337) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-22 01:34:39 (7337) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-22 01:34:39 (7337) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-22 01:34:39 (7337) [INFO]               : yarn
* 2024-08-22 01:34:39 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-22 01:34:39 (7337) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-22 01:34:39 (7354) [INFO] 
* 2024-08-22 01:34:47 (2039) [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-08-22 01:34:47 (2040) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-22 01:34:47 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-22 01:34:49 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vS0LjPVMq6/ea_profile.json
* 2024-08-22 01:34:56 (386) [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/vS0LjPVMq6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-22 01:34:56 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-23 01:33:46 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-23 01:33:46 (8647) [INFO] Newer version of script found. Downloading.
* 2024-08-23 01:33:47 (8656) [INFO] Script update to version 52 successful.
* 2024-08-23 01:33:48 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-23 01:33:48 (2242) [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-08-23 01:33:48 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-23 01:33:48 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-23 01:33:48 (7574) [INFO] 
* 2024-08-23 01:33:52 (673) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-23 01:33:52 (680) [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.

* 2024-08-23 01:33:52 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-23 01:33:52 (7574) [INFO] 
* 2024-08-23 01:34:04 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-23 01:34:04 (2104) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-23 01:34:04 (2104) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-23 01:34:04 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-23 01:34:04 (2080) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-23 01:34:04 (2104) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-23 01:34:04 (2104) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-23 01:34:04 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-23 01:34:04 (2104) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-23 01:34:11 (1963) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-23 01:34:11 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-23 01:34:11 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-23 01:34:11 (7574) [INFO] 
* 2024-08-23 01:34:11 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-23 01:34:11 (7587) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 354340.
* 2024-08-23 01:34:11 (7587) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-23 01:34:11 (7587) [INFO]   The other application is: yum
* 2024-08-23 01:34:11 (7587) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-08-23 01:34:11 (7587) [INFO]     Started: Fri Aug 23 01:33:55 2024 - 00:16 ago
* 2024-08-23 01:34:11 (7587) [INFO]     State  : Sleeping, pid: 354340
* 2024-08-23 01:34:13 (7587) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-23 01:34:13 (7587) [INFO]   The other application is: yum
* 2024-08-23 01:34:13 (7587) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-08-23 01:34:13 (7587) [INFO]     Started: Fri Aug 23 01:33:55 2024 - 00:18 ago
* 2024-08-23 01:34:13 (7587) [INFO]     State  : Sleeping, pid: 354340
* 2024-08-23 01:34:15 (7587) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-23 01:34:15 (7587) [INFO]   The other application is: yum
* 2024-08-23 01:34:15 (7587) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-08-23 01:34:15 (7587) [INFO]     Started: Fri Aug 23 01:33:55 2024 - 00:20 ago
* 2024-08-23 01:34:15 (7587) [INFO]     State  : Sleeping, pid: 354340
* 2024-08-23 01:34:17 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-23 01:34:17 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-23 01:34:17 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-23 01:34:17 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-23 01:34:17 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-23 01:34:17 (7587) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-23 01:34:17 (7587) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-23 01:34:17 (7587) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-23 01:34:17 (7587) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-23 01:34:17 (7587) [INFO]               : yarn
* 2024-08-23 01:34:17 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-23 01:34:17 (7587) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-23 01:34:17 (7604) [INFO] 
* 2024-08-23 01:34:23 (1973) [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-08-23 01:34:23 (1974) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-23 01:34:23 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-23 01:34:26 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F6NX4GpxZ4/ea_profile.json
* 2024-08-23 01:34:32 (390) [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/F6NX4GpxZ4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-23 01:34:32 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-24 01:34:54 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-24 01:34:54 (8939) [INFO] Script is up to date.
* 2024-08-24 01:34:56 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-24 01:34:56 (2242) [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-08-24 01:34:56 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-24 01:34:56 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-24 01:34:56 (7574) [INFO] 
* 2024-08-24 01:35:04 (673) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-24 01:35:04 (680) [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.

* 2024-08-24 01:35:04 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-24 01:35:04 (7574) [INFO] 
* 2024-08-24 01:35:24 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-24 01:35:24 (2104) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-24 01:35:24 (2104) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-24 01:35:24 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-24 01:35:24 (2080) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-24 01:35:24 (2104) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-24 01:35:24 (2104) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-24 01:35:24 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-24 01:35:24 (2104) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-24 01:35:30 (1963) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-24 01:35:30 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-24 01:35:30 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-24 01:35:30 (7574) [INFO] 
* 2024-08-24 01:35:30 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-24 01:35:30 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-24 01:35:30 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-24 01:35:30 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-24 01:35:30 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-24 01:35:30 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-24 01:35:30 (7587) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-24 01:35:30 (7587) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-24 01:35:30 (7587) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-24 01:35:30 (7587) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-24 01:35:30 (7587) [INFO]               : yarn
* 2024-08-24 01:35:30 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-24 01:35:30 (7587) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-24 01:35:30 (7604) [INFO] 
* 2024-08-24 01:35:37 (1973) [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-08-24 01:35:37 (1974) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-24 01:35:37 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-24 01:35:39 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Yr6GnZIEgu/ea_profile.json
* 2024-08-24 01:35:46 (390) [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/Yr6GnZIEgu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-24 01:35:46 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-25 01:34:34 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-25 01:34:34 (8939) [INFO] Script is up to date.
* 2024-08-25 01:34:36 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-25 01:34:36 (2242) [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-08-25 01:34:36 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-25 01:34:36 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-25 01:34:36 (7574) [INFO] 
* 2024-08-25 01:34:42 (673) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-25 01:34:42 (680) [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.

* 2024-08-25 01:34:42 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-25 01:34:42 (7574) [INFO] 
* 2024-08-25 01:35:02 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-25 01:35:02 (2104) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-25 01:35:02 (2104) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-25 01:35:02 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-25 01:35:02 (2080) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-25 01:35:02 (2104) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-25 01:35:02 (2104) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-25 01:35:02 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-25 01:35:02 (2104) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-25 01:35:16 (1963) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 149189.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Sun Aug 25 01:34:51 2024 - 00:11 ago
    State  : Sleeping, pid: 149189
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Sun Aug 25 01:34:51 2024 - 00:13 ago
    State  : Uninterruptible, pid: 149189
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Sun Aug 25 01:34:51 2024 - 00:15 ago
    State  : Uninterruptible, pid: 149189
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (334 MB VSZ)
    Started: Sun Aug 25 01:34:51 2024 - 00:17 ago
    State  : Running, pid: 149189
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-25 01:35:16 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-25 01:35:16 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-25 01:35:16 (7574) [INFO] 
* 2024-08-25 01:35:16 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-25 01:35:17 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-25 01:35:17 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-25 01:35:17 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-25 01:35:17 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-25 01:35:17 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-25 01:35:17 (7587) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-25 01:35:17 (7587) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-25 01:35:17 (7587) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-25 01:35:17 (7587) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-25 01:35:17 (7587) [INFO]               : yarn
* 2024-08-25 01:35:17 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-25 01:35:17 (7587) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-25 01:35:17 (7604) [INFO] 
* 2024-08-25 01:35:29 (1973) [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-08-25 01:35:29 (1974) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-25 01:35:29 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-25 01:35:31 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wqzIvSNJ6R/ea_profile.json
* 2024-08-25 01:35:36 (390) [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/wqzIvSNJ6R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-25 01:35:36 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-26 01:33:36 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-26 01:33:36 (8939) [INFO] Script is up to date.
* 2024-08-26 01:33:37 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-26 01:33:37 (2242) [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-08-26 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-26 01:33:38 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-26 01:33:38 (7574) [INFO] 
* 2024-08-26 01:33:43 (673) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-26 01:33:43 (680) [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.

* 2024-08-26 01:33:43 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-26 01:33:43 (7574) [INFO] 
* 2024-08-26 01:34:00 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-26 01:34:00 (2104) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-26 01:34:00 (2104) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-26 01:34:00 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-26 01:34:00 (2080) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-26 01:34:00 (2104) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-26 01:34:00 (2104) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-26 01:34:00 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-26 01:34:00 (2104) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-26 01:34:06 (1963) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-26 01:34:06 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-26 01:34:06 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-26 01:34:06 (7574) [INFO] 
* 2024-08-26 01:34:06 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-26 01:34:06 (7587) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 640625.
* 2024-08-26 01:34:06 (7587) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-26 01:34:06 (7587) [INFO]   The other application is: yum
* 2024-08-26 01:34:06 (7587) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-08-26 01:34:06 (7587) [INFO]     Started: Mon Aug 26 01:33:55 2024 - 00:11 ago
* 2024-08-26 01:34:06 (7587) [INFO]     State  : Sleeping, pid: 640625
* 2024-08-26 01:34:08 (7587) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-26 01:34:08 (7587) [INFO]   The other application is: yum
* 2024-08-26 01:34:08 (7587) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-08-26 01:34:08 (7587) [INFO]     Started: Mon Aug 26 01:33:55 2024 - 00:13 ago
* 2024-08-26 01:34:08 (7587) [INFO]     State  : Uninterruptible, pid: 640625
* 2024-08-26 01:34:10 (7587) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-26 01:34:10 (7587) [INFO]   The other application is: yum
* 2024-08-26 01:34:10 (7587) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-08-26 01:34:10 (7587) [INFO]     Started: Mon Aug 26 01:33:55 2024 - 00:15 ago
* 2024-08-26 01:34:10 (7587) [INFO]     State  : Running, pid: 640625
* 2024-08-26 01:34:12 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-26 01:34:12 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-26 01:34:12 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-26 01:34:12 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-26 01:34:12 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-26 01:34:12 (7587) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-26 01:34:12 (7587) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-26 01:34:12 (7587) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-26 01:34:12 (7587) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-26 01:34:12 (7587) [INFO]               : yarn
* 2024-08-26 01:34:12 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-26 01:34:12 (7587) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-26 01:34:12 (7604) [INFO] 
* 2024-08-26 01:34:18 (1973) [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-08-26 01:34:18 (1974) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-26 01:34:19 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-26 01:34:20 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EQYiXpgpGj/ea_profile.json
* 2024-08-26 01:34:25 (390) [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/EQYiXpgpGj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-26 01:34:25 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-27 01:33:33 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-27 01:33:33 (8939) [INFO] Script is up to date.
* 2024-08-27 01:33:34 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-27 01:33:34 (2242) [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-08-27 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-27 01:33:34 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-27 01:33:34 (7574) [INFO] 
* 2024-08-27 01:33:39 (673) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-27 01:33:39 (680) [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.

* 2024-08-27 01:33:39 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-27 01:33:39 (7574) [INFO] 
* 2024-08-27 01:33:52 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-27 01:33:52 (2104) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-27 01:33:52 (2104) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-27 01:33:52 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-27 01:33:52 (2080) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-27 01:33:52 (2104) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-27 01:33:52 (2104) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-27 01:33:52 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-27 01:33:52 (2104) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-27 01:33:56 (1963) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-27 01:33:56 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-27 01:33:56 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-27 01:33:56 (7574) [INFO] 
* 2024-08-27 01:33:56 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-27 01:33:56 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-27 01:33:56 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-27 01:33:56 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-27 01:33:56 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-27 01:33:56 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-27 01:33:56 (7587) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-27 01:33:56 (7587) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-27 01:33:56 (7587) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-27 01:33:56 (7587) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-27 01:33:56 (7587) [INFO]               : yarn
* 2024-08-27 01:33:56 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-27 01:33:56 (7587) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-27 01:33:56 (7604) [INFO] 
* 2024-08-27 01:34:02 (1973) [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-08-27 01:34:02 (1974) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-27 01:34:02 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-27 01:34:04 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aiGhYIcscv/ea_profile.json
* 2024-08-27 01:34:09 (390) [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/aiGhYIcscv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-27 01:34:09 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-28 01:33:29 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-28 01:33:29 (8939) [INFO] Script is up to date.
* 2024-08-28 01:33:30 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-28 01:33:30 (2242) [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-08-28 01:33:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-28 01:33:31 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-28 01:33:31 (7574) [INFO] 
* 2024-08-28 01:33:36 (673) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-28 01:33:36 (680) [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.

* 2024-08-28 01:33:36 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-28 01:33:36 (7574) [INFO] 
* 2024-08-28 01:33:59 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-28 01:33:59 (2104) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-28 01:33:59 (2104) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-28 01:33:59 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-28 01:33:59 (2080) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-28 01:33:59 (2104) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-28 01:33:59 (2104) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-28 01:33:59 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-28 01:33:59 (2104) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-28 01:34:04 (1963) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-28 01:34:04 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-28 01:34:04 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-28 01:34:04 (7574) [INFO] 
* 2024-08-28 01:34:05 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-28 01:34:05 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-28 01:34:05 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-28 01:34:05 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-28 01:34:05 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-28 01:34:05 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-28 01:34:05 (7587) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-28 01:34:05 (7587) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-28 01:34:05 (7587) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-28 01:34:05 (7587) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-28 01:34:05 (7587) [INFO]               : yarn
* 2024-08-28 01:34:05 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-28 01:34:05 (7587) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-28 01:34:05 (7604) [INFO] 
* 2024-08-28 01:34:11 (1973) [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-08-28 01:34:11 (1974) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-28 01:34:11 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-28 01:34:12 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TIj8I2ixjT/ea_profile.json
* 2024-08-28 01:34:18 (390) [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/TIj8I2ixjT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-28 01:34:18 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-29 01:33:38 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-29 01:33:38 (8939) [INFO] Script is up to date.
* 2024-08-29 01:33:39 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-29 01:33:39 (2242) [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-08-29 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-29 01:33:39 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-29 01:33:39 (7574) [INFO] 
* 2024-08-29 01:33:46 (673) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-29 01:33:46 (680) [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.

* 2024-08-29 01:33:46 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-29 01:33:46 (7574) [INFO] 
* 2024-08-29 01:34:11 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-29 01:34:11 (2104) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-29 01:34:11 (2104) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-29 01:34:11 (2080) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-29 01:34:11 (2080) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-29 01:34:11 (2104) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-29 01:34:11 (2104) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-29 01:34:11 (2080) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-29 01:34:11 (2104) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-29 01:34:16 (1963) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-29 01:34:16 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-29 01:34:16 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-29 01:34:16 (7574) [INFO] 
* 2024-08-29 01:34:16 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-29 01:34:16 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-29 01:34:16 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-29 01:34:16 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-29 01:34:16 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-29 01:34:16 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-29 01:34:16 (7587) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-29 01:34:16 (7587) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-29 01:34:16 (7587) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-29 01:34:16 (7587) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-29 01:34:16 (7587) [INFO]               : yarn
* 2024-08-29 01:34:16 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-29 01:34:16 (7587) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-29 01:34:16 (7604) [INFO] 
* 2024-08-29 01:34:23 (1973) [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-08-29 01:34:23 (1974) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-29 01:34:23 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-29 01:34:25 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9gDtxLfZVQ/ea_profile.json
* 2024-08-29 01:34:31 (390) [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/9gDtxLfZVQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-29 01:34:31 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-30 01:33:41 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-30 01:33:41 (8922) [INFO] Newer version of script found. Downloading.
* 2024-08-30 01:33:42 (8931) [INFO] Script update to version 53 successful.
* 2024-08-30 01:33:43 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-30 01:33:43 (2245) [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-08-30 01:33:43 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-30 01:33:43 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-30 01:33:43 (7647) [INFO] 
* 2024-08-30 01:34:04 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-30 01:34:04 (683) [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.

* 2024-08-30 01:34:04 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-08-30 01:34:04 (7647) [INFO] 
* 2024-08-30 01:34:12 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-30 01:34:12 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-30 01:34:12 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-30 01:34:12 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-30 01:34:12 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-30 01:34:12 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-30 01:34:12 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-30 01:34:12 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-30 01:34:12 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-30 01:34:17 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-30 01:34:17 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-30 01:34:17 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-08-30 01:34:17 (7647) [INFO] 
* 2024-08-30 01:34:17 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-30 01:34:17 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-30 01:34:17 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-30 01:34:17 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-30 01:34:17 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-30 01:34:17 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-30 01:34:17 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-30 01:34:17 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-30 01:34:17 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-30 01:34:17 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-30 01:34:17 (7660) [INFO]               : yarn
* 2024-08-30 01:34:17 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-08-30 01:34:17 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-30 01:34:17 (7677) [INFO] 
* 2024-08-30 01:34:24 (1976) [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-08-30 01:34:24 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-30 01:34:24 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-30 01:34:25 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tZ9XJUBsQS/ea_profile.json
* 2024-08-30 01:34:31 (391) [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/tZ9XJUBsQS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-08-30 01:34:31 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-31 01:35:28 (8992) [INFO] Self-update of script version 53 requested.
* 2024-08-31 01:35:28 (9014) [INFO] Script is up to date.
* 2024-08-31 01:35:29 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-08-31 01:35:29 (2245) [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-08-31 01:35:30 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-08-31 01:35:30 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-31 01:35:30 (7647) [INFO] 
* 2024-08-31 01:35:42 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-08-31 01:35:42 (683) [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.

* 2024-08-31 01:35:42 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-08-31 01:35:42 (7647) [INFO] 
* 2024-08-31 01:35:51 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-08-31 01:35:51 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-08-31 01:35:51 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-08-31 01:35:51 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-31 01:35:51 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-08-31 01:35:51 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-08-31 01:35:51 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-08-31 01:35:51 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-08-31 01:35:51 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-08-31 01:35:56 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-31 01:35:56 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-31 01:35:56 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-08-31 01:35:56 (7647) [INFO] 
* 2024-08-31 01:35:56 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-31 01:35:56 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-08-31 01:35:56 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-31 01:35:56 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-31 01:35:56 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-08-31 01:35:56 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-31 01:35:56 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-08-31 01:35:56 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-08-31 01:35:56 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-08-31 01:35:56 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-31 01:35:56 (7660) [INFO]               : yarn
* 2024-08-31 01:35:56 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-08-31 01:35:56 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-08-31 01:35:56 (7677) [INFO] 
* 2024-08-31 01:36:02 (1976) [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-08-31 01:36:02 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-08-31 01:36:02 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-31 01:36:03 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gAEZ4xt1kS/ea_profile.json
* 2024-08-31 01:36:08 (391) [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/gAEZ4xt1kS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-08-31 01:36:08 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-01 01:34:42 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-01 01:34:43 (9014) [INFO] Script is up to date.
* 2024-09-01 01:34:44 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-01 01:34:44 (2245) [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-09-01 01:34:44 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-01 01:34:44 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-01 01:34:44 (7647) [INFO] 
* 2024-09-01 01:34:48 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-01 01:34:48 (683) [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.

* 2024-09-01 01:34:48 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-01 01:34:48 (7647) [INFO] 
* 2024-09-01 01:35:12 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-01 01:35:12 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-01 01:35:12 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-01 01:35:12 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-01 01:35:12 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-01 01:35:12 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-01 01:35:12 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-01 01:35:12 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-01 01:35:12 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-01 01:35:17 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-01 01:35:17 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-01 01:35:17 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-01 01:35:17 (7647) [INFO] 
* 2024-09-01 01:35:18 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-01 01:35:18 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-01 01:35:18 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-01 01:35:18 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-01 01:35:18 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-01 01:35:18 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-01 01:35:18 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-01 01:35:18 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-01 01:35:18 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-01 01:35:18 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-01 01:35:18 (7660) [INFO]               : yarn
* 2024-09-01 01:35:18 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-01 01:35:18 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-01 01:35:18 (7677) [INFO] 
* 2024-09-01 01:35:25 (1976) [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-09-01 01:35:25 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-01 01:35:25 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-01 01:35:27 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R2DrUXRbM8/ea_profile.json
* 2024-09-01 01:35:31 (391) [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/R2DrUXRbM8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-01 01:35:31 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-02 01:33:30 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-02 01:33:30 (9014) [INFO] Script is up to date.
* 2024-09-02 01:33:31 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-02 01:33:31 (2245) [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-09-02 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-02 01:33:32 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-02 01:33:32 (7647) [INFO] 
* 2024-09-02 01:33:46 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-02 01:33:46 (683) [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.

* 2024-09-02 01:33:46 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-02 01:33:46 (7647) [INFO] 
* 2024-09-02 01:33:59 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-02 01:33:59 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-02 01:33:59 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-02 01:33:59 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-02 01:33:59 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-02 01:33:59 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-02 01:33:59 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-02 01:33:59 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-02 01:33:59 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-02 01:34:05 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-02 01:34:05 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-02 01:34:05 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-02 01:34:05 (7647) [INFO] 
* 2024-09-02 01:34:05 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-02 01:34:05 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-02 01:34:05 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-02 01:34:05 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-02 01:34:05 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-02 01:34:05 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-02 01:34:05 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-02 01:34:05 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-02 01:34:05 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-02 01:34:05 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-02 01:34:05 (7660) [INFO]               : yarn
* 2024-09-02 01:34:05 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-02 01:34:05 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-02 01:34:05 (7677) [INFO] 
* 2024-09-02 01:34:14 (1976) [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-09-02 01:34:14 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-02 01:34:15 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-02 01:34:16 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tzSF1vWAg9/ea_profile.json
* 2024-09-02 01:34:23 (391) [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/tzSF1vWAg9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-02 01:34:23 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-03 01:34:10 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-03 01:34:10 (9014) [INFO] Script is up to date.
* 2024-09-03 01:34:11 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-03 01:34:11 (2245) [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-09-03 01:34:13 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-03 01:34:13 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-03 01:34:13 (7647) [INFO] 
* 2024-09-03 01:34:17 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-03 01:34:17 (683) [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.

* 2024-09-03 01:34:17 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-03 01:34:17 (7647) [INFO] 
* 2024-09-03 01:34:35 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-03 01:34:35 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-03 01:34:35 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-03 01:34:35 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-03 01:34:35 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-03 01:34:35 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-03 01:34:35 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-03 01:34:35 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-03 01:34:35 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-03 01:34:43 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-03 01:34:43 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-03 01:34:43 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-03 01:34:43 (7647) [INFO] 
* 2024-09-03 01:34:43 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-03 01:34:44 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-03 01:34:44 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-03 01:34:44 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-03 01:34:44 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-03 01:34:44 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-03 01:34:44 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-03 01:34:44 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-03 01:34:44 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-03 01:34:44 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-03 01:34:44 (7660) [INFO]               : yarn
* 2024-09-03 01:34:44 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-03 01:34:44 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-03 01:34:44 (7677) [INFO] 
* 2024-09-03 01:34:56 (1976) [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-09-03 01:34:56 (1977) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 14112.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Tue Sep  3 01:34:21 2024 - 00:23 ago
    State  : Sleeping, pid: 14112
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.8 GB VSZ)
    Started: Tue Sep  3 01:34:21 2024 - 00:25 ago
    State  : Sleeping, pid: 14112
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Tue Sep  3 01:34:21 2024 - 00:27 ago
    State  : Uninterruptible, pid: 14112
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-03 01:34:56 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-03 01:34:58 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4MLDehN0Fg/ea_profile.json
* 2024-09-03 01:35:10 (391) [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/4MLDehN0Fg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-03 01:35:10 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-04 01:33:39 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-04 01:33:39 (9014) [INFO] Script is up to date.
* 2024-09-04 01:33:40 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-04 01:33:40 (2245) [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-09-04 01:33:40 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-04 01:33:40 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-04 01:33:40 (7647) [INFO] 
* 2024-09-04 01:33:48 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-04 01:33:48 (683) [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.

* 2024-09-04 01:33:48 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-04 01:33:48 (7647) [INFO] 
* 2024-09-04 01:33:57 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-04 01:33:57 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-04 01:33:57 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-04 01:33:57 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-04 01:33:57 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-04 01:33:57 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-04 01:33:57 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-04 01:33:57 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-04 01:33:57 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-04 01:34:03 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-04 01:34:03 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-04 01:34:03 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-04 01:34:03 (7647) [INFO] 
* 2024-09-04 01:34:03 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-04 01:34:03 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-04 01:34:03 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-04 01:34:03 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-04 01:34:03 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-04 01:34:03 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-04 01:34:03 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-04 01:34:03 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-04 01:34:03 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-04 01:34:03 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-04 01:34:03 (7660) [INFO]               : yarn
* 2024-09-04 01:34:03 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-04 01:34:03 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-04 01:34:03 (7677) [INFO] 
* 2024-09-04 01:34:12 (1976) [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-09-04 01:34:12 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-04 01:34:12 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-04 01:34:13 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/o4TLKd_n6s/ea_profile.json
* 2024-09-04 01:34:17 (391) [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/o4TLKd_n6s/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-04 01:34:17 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-05 01:34:36 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-05 01:34:36 (9014) [INFO] Script is up to date.
* 2024-09-05 01:34:37 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-05 01:34:37 (2245) [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-09-05 01:34:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-05 01:34:37 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-05 01:34:37 (7647) [INFO] 
* 2024-09-05 01:34:45 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-05 01:34:45 (683) [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.

* 2024-09-05 01:34:45 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-05 01:34:45 (7647) [INFO] 
* 2024-09-05 01:35:16 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-05 01:35:17 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-05 01:35:17 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-05 01:35:17 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-05 01:35:17 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-05 01:35:17 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-05 01:35:17 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-05 01:35:17 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-05 01:35:17 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-05 01:35:22 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-05 01:35:22 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-05 01:35:22 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-05 01:35:22 (7647) [INFO] 
* 2024-09-05 01:35:22 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-05 01:35:23 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-05 01:35:23 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-05 01:35:23 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-05 01:35:23 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-05 01:35:23 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-05 01:35:23 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-05 01:35:23 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-05 01:35:23 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-05 01:35:23 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-05 01:35:23 (7660) [INFO]               : yarn
* 2024-09-05 01:35:23 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-05 01:35:23 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-05 01:35:23 (7677) [INFO] 
* 2024-09-05 01:35:30 (1976) [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-09-05 01:35:30 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-05 01:35:31 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-05 01:35:33 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wlVHJ_llZU/ea_profile.json
* 2024-09-05 01:35:42 (391) [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/wlVHJ_llZU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-05 01:35:42 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-06 01:34:48 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-06 01:34:48 (9014) [INFO] Script is up to date.
* 2024-09-06 01:34:49 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-06 01:34:49 (2245) [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-09-06 01:34:49 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-06 01:34:49 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-06 01:34:49 (7647) [INFO] 
* 2024-09-06 01:35:13 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-06 01:35:13 (683) [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.

* 2024-09-06 01:35:14 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-06 01:35:14 (7647) [INFO] 
* 2024-09-06 01:35:27 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-06 01:35:27 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-06 01:35:27 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-06 01:35:27 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-06 01:35:27 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-06 01:35:27 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-06 01:35:27 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-06 01:35:27 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-06 01:35:27 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-06 01:35:33 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-06 01:35:33 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-06 01:35:33 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-06 01:35:33 (7647) [INFO] 
* 2024-09-06 01:35:33 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-06 01:35:34 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-06 01:35:34 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-06 01:35:34 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-06 01:35:34 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-06 01:35:34 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-06 01:35:34 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-06 01:35:34 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-06 01:35:34 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-06 01:35:34 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-06 01:35:34 (7660) [INFO]               : yarn
* 2024-09-06 01:35:34 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-06 01:35:34 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-06 01:35:34 (7677) [INFO] 
* 2024-09-06 01:35:41 (1976) [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-09-06 01:35:41 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-06 01:35:41 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-06 01:35:55 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0TLQ720Vuj/ea_profile.json
* 2024-09-06 01:36:07 (391) [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/0TLQ720Vuj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-06 01:36:07 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-07 01:40:49 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-07 01:40:49 (9014) [INFO] Script is up to date.
* 2024-09-07 01:40:50 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-07 01:40:50 (2245) [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-09-07 01:40:51 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-07 01:40:51 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-07 01:40:51 (7647) [INFO] 
* 2024-09-07 01:40:59 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-07 01:40:59 (683) [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.

* 2024-09-07 01:40:59 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-07 01:40:59 (7647) [INFO] 
* 2024-09-07 01:41:15 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-07 01:41:15 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-07 01:41:15 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-07 01:41:15 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-07 01:41:15 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-07 01:41:15 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-07 01:41:15 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-07 01:41:15 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-07 01:41:15 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-07 01:41:23 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-07 01:41:23 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-07 01:41:23 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-07 01:41:23 (7647) [INFO] 
* 2024-09-07 01:41:23 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-07 01:41:23 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-07 01:41:23 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-07 01:41:23 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-07 01:41:23 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-07 01:41:23 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-07 01:41:23 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-07 01:41:23 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-07 01:41:23 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-07 01:41:23 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-07 01:41:23 (7660) [INFO]               : yarn
* 2024-09-07 01:41:23 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-07 01:41:23 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-07 01:41:23 (7677) [INFO] 
* 2024-09-07 01:41:32 (1976) [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-09-07 01:41:32 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-07 01:41:32 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-07 01:41:48 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dPU6GDMOvh/ea_profile.json
* 2024-09-07 01:41:55 (391) [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/dPU6GDMOvh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-07 01:41:55 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-08 01:36:27 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-08 01:36:27 (9014) [INFO] Script is up to date.
* 2024-09-08 01:36:29 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-08 01:36:29 (2245) [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-09-08 01:36:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-08 01:36:29 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-08 01:36:29 (7647) [INFO] 
* 2024-09-08 01:36:36 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-08 01:36:36 (683) [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.

* 2024-09-08 01:36:36 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-08 01:36:36 (7647) [INFO] 
* 2024-09-08 01:36:56 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-08 01:36:56 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-08 01:36:56 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-08 01:36:56 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-08 01:36:56 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-08 01:36:56 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-08 01:36:56 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-08 01:36:56 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-08 01:36:56 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-08 01:37:03 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-08 01:37:03 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-08 01:37:03 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-08 01:37:03 (7647) [INFO] 
* 2024-09-08 01:37:03 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-08 01:37:03 (7660) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 755185.
* 2024-09-08 01:37:03 (7660) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-09-08 01:37:03 (7660) [INFO]   The other application is: yum
* 2024-09-08 01:37:03 (7660) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-09-08 01:37:03 (7660) [INFO]     Started: Sun Sep  8 01:36:41 2024 - 00:22 ago
* 2024-09-08 01:37:03 (7660) [INFO]     State  : Sleeping, pid: 755185
* 2024-09-08 01:37:05 (7660) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-09-08 01:37:05 (7660) [INFO]   The other application is: yum
* 2024-09-08 01:37:05 (7660) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-09-08 01:37:05 (7660) [INFO]     Started: Sun Sep  8 01:36:41 2024 - 00:24 ago
* 2024-09-08 01:37:05 (7660) [INFO]     State  : Sleeping, pid: 755185
* 2024-09-08 01:37:07 (7660) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-09-08 01:37:07 (7660) [INFO]   The other application is: yum
* 2024-09-08 01:37:07 (7660) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-09-08 01:37:07 (7660) [INFO]     Started: Sun Sep  8 01:36:41 2024 - 00:26 ago
* 2024-09-08 01:37:07 (7660) [INFO]     State  : Uninterruptible, pid: 755185
* 2024-09-08 01:37:09 (7660) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-09-08 01:37:09 (7660) [INFO]   The other application is: yum
* 2024-09-08 01:37:09 (7660) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-09-08 01:37:09 (7660) [INFO]     Started: Sun Sep  8 01:36:41 2024 - 00:28 ago
* 2024-09-08 01:37:09 (7660) [INFO]     State  : Uninterruptible, pid: 755185
* 2024-09-08 01:37:11 (7660) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-09-08 01:37:11 (7660) [INFO]   The other application is: yum
* 2024-09-08 01:37:11 (7660) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-09-08 01:37:11 (7660) [INFO]     Started: Sun Sep  8 01:36:41 2024 - 00:30 ago
* 2024-09-08 01:37:11 (7660) [INFO]     State  : Sleeping, pid: 755185
* 2024-09-08 01:37:13 (7660) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-09-08 01:37:13 (7660) [INFO]   The other application is: yum
* 2024-09-08 01:37:13 (7660) [INFO]     Memory :  40 M RSS (334 MB VSZ)
* 2024-09-08 01:37:13 (7660) [INFO]     Started: Sun Sep  8 01:36:41 2024 - 00:32 ago
* 2024-09-08 01:37:13 (7660) [INFO]     State  : Uninterruptible, pid: 755185
* 2024-09-08 01:37:15 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-08 01:37:15 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-08 01:37:15 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-08 01:37:15 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-08 01:37:15 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-08 01:37:15 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-08 01:37:15 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-08 01:37:15 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-08 01:37:15 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-08 01:37:15 (7660) [INFO]               : yarn
* 2024-09-08 01:37:15 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-08 01:37:15 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-08 01:37:15 (7677) [INFO] 
* 2024-09-08 01:37:23 (1976) [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-09-08 01:37:23 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-08 01:37:23 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-08 01:37:24 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/K7H5SI49vL/ea_profile.json
* 2024-09-08 01:37:30 (391) [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/K7H5SI49vL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-08 01:37:30 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-09 01:33:55 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-09 01:33:55 (9014) [INFO] Script is up to date.
* 2024-09-09 01:33:56 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-09 01:33:56 (2245) [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-09-09 01:33:57 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-09 01:33:57 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-09 01:33:57 (7647) [INFO] 
* 2024-09-09 01:34:04 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-09 01:34:04 (683) [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.

* 2024-09-09 01:34:04 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-09 01:34:04 (7647) [INFO] 
* 2024-09-09 01:34:23 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-09 01:34:23 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-09 01:34:23 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-09 01:34:23 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-09 01:34:23 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-09 01:34:23 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-09 01:34:23 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-09 01:34:23 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-09 01:34:23 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-09 01:34:31 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-09 01:34:31 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-09 01:34:31 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-09 01:34:31 (7647) [INFO] 
* 2024-09-09 01:34:31 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-09 01:34:32 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-09 01:34:32 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-09 01:34:32 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-09 01:34:32 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-09 01:34:32 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-09 01:34:32 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-09 01:34:32 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-09 01:34:32 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-09 01:34:32 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-09 01:34:32 (7660) [INFO]               : yarn
* 2024-09-09 01:34:32 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-09 01:34:32 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-09 01:34:32 (7677) [INFO] 
* 2024-09-09 01:34:38 (1976) [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-09-09 01:34:38 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-09 01:34:38 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-09 01:34:40 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cWleDJXvwA/ea_profile.json
* 2024-09-09 01:34:47 (391) [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/cWleDJXvwA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-09 01:34:47 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-10 01:33:25 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-10 01:33:25 (9014) [INFO] Script is up to date.
* 2024-09-10 01:33:26 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-10 01:33:26 (2245) [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-09-10 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-10 01:33:27 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-10 01:33:27 (7647) [INFO] 
* 2024-09-10 01:33:32 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-10 01:33:32 (683) [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.

* 2024-09-10 01:33:32 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-10 01:33:32 (7647) [INFO] 
* 2024-09-10 01:33:49 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-10 01:33:49 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-10 01:33:49 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-10 01:33:49 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-10 01:33:49 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-10 01:33:49 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-10 01:33:49 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-10 01:33:49 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-10 01:33:49 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-10 01:34:00 (1966) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 553452.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Tue Sep 10 01:33:41 2024 - 00:08 ago
    State  : Sleeping, pid: 553452
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Tue Sep 10 01:33:41 2024 - 00:10 ago
    State  : Sleeping, pid: 553452
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Tue Sep 10 01:33:41 2024 - 00:12 ago
    State  : Sleeping, pid: 553452
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-10 01:34:00 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-10 01:34:00 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-10 01:34:00 (7647) [INFO] 
* 2024-09-10 01:34:00 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-10 01:34:00 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-10 01:34:00 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-10 01:34:00 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-10 01:34:00 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-10 01:34:00 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-10 01:34:00 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-10 01:34:00 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-10 01:34:00 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-10 01:34:00 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-10 01:34:00 (7660) [INFO]               : yarn
* 2024-09-10 01:34:00 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-10 01:34:00 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-10 01:34:00 (7677) [INFO] 
* 2024-09-10 01:34:12 (1976) [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-09-10 01:34:12 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-10 01:34:12 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-10 01:34:13 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R1ALdr37j3/ea_profile.json
* 2024-09-10 01:34:19 (391) [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/R1ALdr37j3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-10 01:34:19 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-11 01:33:24 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-11 01:33:24 (9014) [INFO] Script is up to date.
* 2024-09-11 01:33:25 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-11 01:33:25 (2245) [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-09-11 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-11 01:33:25 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-11 01:33:25 (7647) [INFO] 
* 2024-09-11 01:33:29 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-11 01:33:29 (683) [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.

* 2024-09-11 01:33:29 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-11 01:33:29 (7647) [INFO] 
* 2024-09-11 01:33:55 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-11 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-11 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-11 01:33:55 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-11 01:33:55 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-11 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-11 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-11 01:33:55 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-11 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-11 01:34:00 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-11 01:34:00 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-11 01:34:00 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-11 01:34:00 (7647) [INFO] 
* 2024-09-11 01:34:00 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-11 01:34:00 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-11 01:34:00 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-11 01:34:00 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-11 01:34:00 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-11 01:34:00 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-11 01:34:00 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-11 01:34:00 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-11 01:34:00 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-11 01:34:00 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-11 01:34:00 (7660) [INFO]               : yarn
* 2024-09-11 01:34:00 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-11 01:34:00 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-11 01:34:00 (7677) [INFO] 
* 2024-09-11 01:34:05 (1976) [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-09-11 01:34:05 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-11 01:34:06 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-11 01:34:07 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/axGQQPGFY1/ea_profile.json
* 2024-09-11 01:34:12 (391) [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/axGQQPGFY1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-11 01:34:12 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-12 01:33:27 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-12 01:33:27 (9014) [INFO] Script is up to date.
* 2024-09-12 01:33:28 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-12 01:33:28 (2245) [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-09-12 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-12 01:33:28 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-12 01:33:28 (7647) [INFO] 
* 2024-09-12 01:33:32 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-12 01:33:32 (683) [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.

* 2024-09-12 01:33:32 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-12 01:33:32 (7647) [INFO] 
* 2024-09-12 01:33:55 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-12 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-12 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-12 01:33:55 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-12 01:33:55 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-12 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-12 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-12 01:33:55 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-12 01:33:55 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-12 01:33:59 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-12 01:33:59 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-12 01:33:59 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-12 01:33:59 (7647) [INFO] 
* 2024-09-12 01:34:00 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-12 01:34:00 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-12 01:34:00 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-12 01:34:00 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-12 01:34:00 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-12 01:34:00 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-12 01:34:00 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-12 01:34:00 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-12 01:34:00 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-12 01:34:00 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-12 01:34:00 (7660) [INFO]               : yarn
* 2024-09-12 01:34:00 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-12 01:34:00 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-12 01:34:00 (7677) [INFO] 
* 2024-09-12 01:34:08 (1976) [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-09-12 01:34:08 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-12 01:34:08 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-12 01:34:09 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pAH2WyhZ3j/ea_profile.json
* 2024-09-12 01:34:13 (391) [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/pAH2WyhZ3j/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-12 01:34:13 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-13 01:33:29 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-13 01:33:29 (9014) [INFO] Script is up to date.
* 2024-09-13 01:33:30 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-13 01:33:30 (2245) [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-09-13 01:33:30 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-13 01:33:30 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-13 01:33:30 (7647) [INFO] 
* 2024-09-13 01:33:35 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-13 01:33:35 (683) [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.

* 2024-09-13 01:33:35 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-13 01:33:35 (7647) [INFO] 
* 2024-09-13 01:33:53 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-13 01:33:53 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-13 01:33:53 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-13 01:33:53 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-13 01:33:53 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-13 01:33:53 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-13 01:33:53 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-13 01:33:53 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-13 01:33:53 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-13 01:33:59 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-13 01:33:59 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-13 01:33:59 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-13 01:33:59 (7647) [INFO] 
* 2024-09-13 01:33:59 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-13 01:33:59 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-13 01:33:59 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-13 01:33:59 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-13 01:33:59 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-13 01:33:59 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-13 01:33:59 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-13 01:33:59 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-13 01:33:59 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-13 01:33:59 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-13 01:33:59 (7660) [INFO]               : yarn
* 2024-09-13 01:33:59 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-13 01:33:59 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-13 01:33:59 (7677) [INFO] 
* 2024-09-13 01:34:04 (1976) [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-09-13 01:34:04 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-13 01:34:05 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-13 01:34:06 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uzS46PHfyu/ea_profile.json
* 2024-09-13 01:34:10 (391) [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/uzS46PHfyu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-13 01:34:10 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-14 01:34:05 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-14 01:34:05 (9014) [INFO] Script is up to date.
* 2024-09-14 01:34:06 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-14 01:34:06 (2245) [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-09-14 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-14 01:34:08 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-14 01:34:08 (7647) [INFO] 
* 2024-09-14 01:34:15 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-14 01:34:15 (683) [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.

* 2024-09-14 01:34:15 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-14 01:34:15 (7647) [INFO] 
* 2024-09-14 01:34:20 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-14 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-14 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-14 01:34:20 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-14 01:34:20 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-14 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-14 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-14 01:34:20 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-14 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-14 01:34:24 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-14 01:34:24 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-14 01:34:24 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-14 01:34:24 (7647) [INFO] 
* 2024-09-14 01:34:24 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-14 01:34:25 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-14 01:34:25 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-14 01:34:25 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-14 01:34:25 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-14 01:34:25 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-14 01:34:25 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-14 01:34:25 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-14 01:34:25 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-14 01:34:25 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-14 01:34:25 (7660) [INFO]               : yarn
* 2024-09-14 01:34:25 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-14 01:34:25 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-14 01:34:25 (7677) [INFO] 
* 2024-09-14 01:34:31 (1976) [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-09-14 01:34:31 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-14 01:34:31 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-14 01:34:32 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/voqG_rr5Bg/ea_profile.json
* 2024-09-14 01:34:35 (391) [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/voqG_rr5Bg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-14 01:34:35 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-15 01:33:58 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-15 01:33:58 (9014) [INFO] Script is up to date.
* 2024-09-15 01:33:59 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-15 01:33:59 (2245) [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-09-15 01:33:59 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-15 01:34:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-15 01:34:00 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-15 01:34:00 (7647) [INFO] 
* 2024-09-15 01:34:07 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-15 01:34:07 (683) [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.

* 2024-09-15 01:34:07 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-15 01:34:07 (7647) [INFO] 
* 2024-09-15 01:34:20 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-15 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-15 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-15 01:34:20 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-15 01:34:20 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-15 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-15 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-15 01:34:20 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-15 01:34:20 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-15 01:34:24 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-15 01:34:24 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-15 01:34:24 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-15 01:34:24 (7647) [INFO] 
* 2024-09-15 01:34:25 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-15 01:34:25 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-15 01:34:25 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-15 01:34:25 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-15 01:34:25 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-15 01:34:25 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-15 01:34:25 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-15 01:34:25 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-15 01:34:25 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-15 01:34:25 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-15 01:34:25 (7660) [INFO]               : yarn
* 2024-09-15 01:34:25 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-15 01:34:25 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-15 01:34:25 (7677) [INFO] 
* 2024-09-15 01:34:31 (1976) [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-09-15 01:34:31 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-15 01:34:31 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-15 01:34:32 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/I64awFhCBh/ea_profile.json
* 2024-09-15 01:34:37 (391) [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/I64awFhCBh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-15 01:34:37 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-16 01:33:25 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-16 01:33:25 (9014) [INFO] Script is up to date.
* 2024-09-16 01:33:26 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-16 01:33:26 (2245) [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-09-16 01:33:26 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-16 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-16 01:33:26 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-16 01:33:26 (7647) [INFO] 
* 2024-09-16 01:33:30 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-16 01:33:30 (683) [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.

* 2024-09-16 01:33:30 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-16 01:33:30 (7647) [INFO] 
* 2024-09-16 01:33:47 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-16 01:33:47 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-16 01:33:47 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-16 01:33:47 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-16 01:33:47 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-16 01:33:47 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-16 01:33:47 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-16 01:33:47 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-16 01:33:47 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-16 01:33:52 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-16 01:33:52 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-16 01:33:52 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-16 01:33:52 (7647) [INFO] 
* 2024-09-16 01:33:52 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-16 01:33:52 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-16 01:33:52 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-16 01:33:52 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-16 01:33:52 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-16 01:33:52 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-16 01:33:52 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-16 01:33:52 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-16 01:33:52 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-16 01:33:52 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-16 01:33:52 (7660) [INFO]               : yarn
* 2024-09-16 01:33:52 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-16 01:33:52 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-16 01:33:52 (7677) [INFO] 
* 2024-09-16 01:33:58 (1976) [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-09-16 01:33:58 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-16 01:33:58 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-16 01:33:59 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OOpZouL6zn/ea_profile.json
* 2024-09-16 01:34:04 (391) [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/OOpZouL6zn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-16 01:34:04 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-17 01:33:26 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-17 01:33:26 (9014) [INFO] Script is up to date.
* 2024-09-17 01:33:27 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-17 01:33:27 (2245) [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-09-17 01:33:27 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-17 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-17 01:33:27 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-17 01:33:27 (7647) [INFO] 
* 2024-09-17 01:33:31 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-17 01:33:31 (683) [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.

* 2024-09-17 01:33:31 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-17 01:33:31 (7647) [INFO] 
* 2024-09-17 01:33:48 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-17 01:33:48 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-17 01:33:48 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-17 01:33:48 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-17 01:33:48 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-17 01:33:48 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-17 01:33:48 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-17 01:33:48 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-17 01:33:48 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-17 01:33:52 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-17 01:33:52 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-17 01:33:52 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-17 01:33:52 (7647) [INFO] 
* 2024-09-17 01:33:52 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-17 01:33:52 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-17 01:33:52 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-17 01:33:52 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-17 01:33:52 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-17 01:33:52 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-17 01:33:52 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-17 01:33:52 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-17 01:33:52 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-17 01:33:52 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-17 01:33:52 (7660) [INFO]               : yarn
* 2024-09-17 01:33:52 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-17 01:33:52 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-17 01:33:52 (7677) [INFO] 
* 2024-09-17 01:33:58 (1976) [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-09-17 01:33:58 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-17 01:33:59 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-17 01:34:00 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PfsfHztuNH/ea_profile.json
* 2024-09-17 01:34:05 (391) [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/PfsfHztuNH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-17 01:34:05 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-18 01:33:21 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-18 01:33:21 (9014) [INFO] Script is up to date.
* 2024-09-18 01:33:22 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-18 01:33:22 (2245) [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-09-18 01:33:22 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-18 01:33:22 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-18 01:33:22 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-18 01:33:22 (7647) [INFO] 
* 2024-09-18 01:33:27 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-18 01:33:27 (683) [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.

* 2024-09-18 01:33:27 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-18 01:33:27 (7647) [INFO] 
* 2024-09-18 01:33:50 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-18 01:33:50 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-18 01:33:50 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-18 01:33:50 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-18 01:33:50 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-18 01:33:50 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-18 01:33:50 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-18 01:33:50 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-18 01:33:50 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-18 01:33:54 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-18 01:33:54 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-18 01:33:54 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-18 01:33:54 (7647) [INFO] 
* 2024-09-18 01:33:54 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-18 01:33:54 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-18 01:33:54 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-18 01:33:54 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-18 01:33:54 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-18 01:33:54 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-18 01:33:54 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-18 01:33:54 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-18 01:33:54 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-18 01:33:54 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-18 01:33:54 (7660) [INFO]               : yarn
* 2024-09-18 01:33:54 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-18 01:33:54 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-18 01:33:55 (7677) [INFO] 
* 2024-09-18 01:34:00 (1976) [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-09-18 01:34:00 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-18 01:34:00 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-18 01:34:01 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FCAxbcbytD/ea_profile.json
* 2024-09-18 01:34:06 (391) [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/FCAxbcbytD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-18 01:34:06 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-19 01:34:17 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-19 01:34:17 (9014) [INFO] Script is up to date.
* 2024-09-19 01:34:18 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-19 01:34:18 (2245) [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-09-19 01:34:18 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-19 01:34:19 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-19 01:34:19 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-19 01:34:19 (7647) [INFO] 
* 2024-09-19 01:34:25 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-19 01:34:25 (683) [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.

* 2024-09-19 01:34:25 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-19 01:34:25 (7647) [INFO] 
* 2024-09-19 01:34:39 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-19 01:34:39 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-19 01:34:39 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-19 01:34:39 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-19 01:34:39 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-19 01:34:39 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-19 01:34:39 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-19 01:34:39 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-19 01:34:39 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-19 01:34:44 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-19 01:34:44 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-19 01:34:44 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-19 01:34:44 (7647) [INFO] 
* 2024-09-19 01:34:44 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-19 01:34:44 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-19 01:34:44 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-19 01:34:44 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-19 01:34:44 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-19 01:34:44 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-19 01:34:44 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-19 01:34:44 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-19 01:34:44 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-19 01:34:44 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-19 01:34:44 (7660) [INFO]               : yarn
* 2024-09-19 01:34:44 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-19 01:34:44 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-19 01:34:44 (7677) [INFO] 
* 2024-09-19 01:34:51 (1976) [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-09-19 01:34:51 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-19 01:34:51 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-19 01:34:53 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/a8qF4_3oZO/ea_profile.json
* 2024-09-19 01:34:57 (391) [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/a8qF4_3oZO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-19 01:34:57 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-20 01:33:27 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-20 01:33:27 (9014) [INFO] Script is up to date.
* 2024-09-20 01:33:28 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-20 01:33:28 (2245) [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-09-20 01:33:28 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-20 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-20 01:33:28 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-20 01:33:28 (7647) [INFO] 
* 2024-09-20 01:33:32 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-20 01:33:32 (683) [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.

* 2024-09-20 01:33:32 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-20 01:33:32 (7647) [INFO] 
* 2024-09-20 01:33:46 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-20 01:33:46 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-20 01:33:46 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-20 01:33:46 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-20 01:33:46 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-20 01:33:46 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-20 01:33:46 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-20 01:33:46 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-20 01:33:46 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-20 01:33:50 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-20 01:33:50 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-20 01:33:50 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-20 01:33:50 (7647) [INFO] 
* 2024-09-20 01:33:50 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-20 01:33:50 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-20 01:33:50 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-20 01:33:50 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-20 01:33:50 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-20 01:33:50 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-20 01:33:50 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-20 01:33:50 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-20 01:33:50 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-20 01:33:50 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-20 01:33:50 (7660) [INFO]               : yarn
* 2024-09-20 01:33:50 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-20 01:33:50 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-20 01:33:50 (7677) [INFO] 
* 2024-09-20 01:33:55 (1976) [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-09-20 01:33:55 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-20 01:33:55 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-20 01:33:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vOOX8QoVqX/ea_profile.json
* 2024-09-20 01:34:01 (391) [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/vOOX8QoVqX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-20 01:34:01 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-21 01:34:02 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-21 01:34:02 (9014) [INFO] Script is up to date.
* 2024-09-21 01:34:03 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-21 01:34:03 (2245) [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-09-21 01:34:03 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-21 01:34:03 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-21 01:34:03 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-21 01:34:03 (7647) [INFO] 
* 2024-09-21 01:34:08 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-21 01:34:08 (683) [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.

* 2024-09-21 01:34:08 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-21 01:34:08 (7647) [INFO] 
* 2024-09-21 01:34:26 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-21 01:34:26 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-21 01:34:26 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-21 01:34:26 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-21 01:34:26 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-21 01:34:26 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-21 01:34:26 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-21 01:34:26 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-21 01:34:26 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-21 01:34:31 (1966) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-21 01:34:31 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-21 01:34:31 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-21 01:34:31 (7647) [INFO] 
* 2024-09-21 01:34:31 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-21 01:34:31 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-21 01:34:31 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-21 01:34:31 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-21 01:34:31 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-21 01:34:31 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-21 01:34:31 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-21 01:34:31 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-21 01:34:31 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-21 01:34:31 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-21 01:34:31 (7660) [INFO]               : yarn
* 2024-09-21 01:34:31 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-21 01:34:31 (7660) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-21 01:34:31 (7677) [INFO] 
* 2024-09-21 01:34:38 (1976) [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-09-21 01:34:38 (1977) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-21 01:34:38 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-21 01:34:39 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Zvxa7EWTlr/ea_profile.json
* 2024-09-21 01:34:43 (391) [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/Zvxa7EWTlr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-21 01:34:43 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-22 01:34:00 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-22 01:34:00 (9014) [INFO] Script is up to date.
* 2024-09-22 01:34:01 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-22 01:34:01 (2245) [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-09-22 01:34:01 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-22 01:34:01 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-22 01:34:01 (231) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.40) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.41.

* 2024-09-22 01:34:01 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-22 01:34:01 (7647) [INFO] 
* 2024-09-22 01:34:06 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-22 01:34:06 (683) [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.

* 2024-09-22 01:34:06 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-22 01:34:06 (7647) [INFO] 
* 2024-09-22 01:34:11 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-22 01:34:11 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-22 01:34:11 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-22 01:34:11 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-22 01:34:11 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-22 01:34:11 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-22 01:34:11 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-22 01:34:11 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-22 01:34:11 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-22 01:34:12 (1966) [WARN] Initial run of "yum makecache" failed: 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-09-22 01:34:12 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-22 01:34:12 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-22 01:34:12 (7647) [INFO] 
* 2024-09-22 01:34:12 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-22 01:34:12 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-22 01:34:12 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-22 01:34:12 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-22 01:34:12 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-22 01:34:12 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-22 01:34:12 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-22 01:34:12 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-22 01:34:12 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-22 01:34:12 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-22 01:34:12 (7660) [INFO]               : yarn
* 2024-09-22 01:34:12 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-22 01:34:12 (7660) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-09-22 01:34:12 (7677) [INFO] 
* 2024-09-22 01:34:15 (1976) [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-09-22 01:34:15 (1977) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-09-22 01:34:15 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-22 01:34:16 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vg8VqnwuFV/ea_profile.json
* 2024-09-22 01:34:17 (391) [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/vg8VqnwuFV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-22 01:34:17 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-23 01:33:25 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-23 01:33:25 (9014) [INFO] Script is up to date.
* 2024-09-23 01:33:26 (231) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-23 01:33:26 (2245) [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-09-23 01:33:26 (231) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-09-23 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-23 01:33:26 (231) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.40) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.41.

* 2024-09-23 01:33:26 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-23 01:33:26 (7647) [INFO] 
* 2024-09-23 01:33:30 (676) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-23 01:33:30 (683) [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.

* 2024-09-23 01:33:30 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-23 01:33:30 (7647) [INFO] 
* 2024-09-23 01:33:32 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-23 01:33:32 (2107) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-23 01:33:32 (2107) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-23 01:33:32 (2083) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-23 01:33:32 (2083) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-23 01:33:32 (2107) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-23 01:33:32 (2107) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-23 01:33:32 (2083) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-23 01:33:32 (2107) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-23 01:33:34 (1966) [WARN] Initial run of "yum makecache" failed: 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-09-23 01:33:34 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-23 01:33:34 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-23 01:33:34 (7647) [INFO] 
* 2024-09-23 01:33:34 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-23 01:33:34 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-23 01:33:34 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-23 01:33:34 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-23 01:33:34 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-23 01:33:34 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-23 01:33:34 (7660) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-23 01:33:34 (7660) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-23 01:33:34 (7660) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-23 01:33:34 (7660) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-23 01:33:34 (7660) [INFO]               : yarn
* 2024-09-23 01:33:34 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-23 01:33:34 (7660) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-09-23 01:33:34 (7677) [INFO] 
* 2024-09-23 01:33:37 (1976) [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-09-23 01:33:37 (1977) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-09-23 01:33:37 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-23 01:33:38 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SwwUzvFRxm/ea_profile.json
* 2024-09-23 01:33:39 (391) [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/SwwUzvFRxm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-23 01:33:39 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-24 01:34:06 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-24 01:34:07 (8997) [INFO] Newer version of script found. Downloading.
* 2024-09-24 01:34:08 (9006) [INFO] Script update to version 54 successful.
* 2024-09-24 01:34:09 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-24 01:34:09 (2274) [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-09-24 01:34:15 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-24 01:34:15 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-24 01:34:15 (7667) [INFO] 
* 2024-09-24 01:34:20 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-24 01:34:20 (682) [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.

* 2024-09-24 01:34:20 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-24 01:34:20 (7667) [INFO] 
* 2024-09-24 01:34:30 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-24 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-24 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-24 01:34:30 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-24 01:34:30 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-24 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-24 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-24 01:34:30 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-24 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-24 01:34:35 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-24 01:34:35 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-24 01:34:35 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-24 01:34:35 (7667) [INFO] 
* 2024-09-24 01:34:35 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-24 01:34:35 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-24 01:34:35 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-24 01:34:35 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-24 01:34:35 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-24 01:34:35 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-24 01:34:35 (7680) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-24 01:34:35 (7680) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-24 01:34:35 (7680) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-24 01:34:35 (7680) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-24 01:34:35 (7680) [INFO]               : yarn
* 2024-09-24 01:34:35 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-24 01:34:35 (7680) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-24 01:34:35 (7697) [INFO] 
* 2024-09-24 01:34:41 (2005) [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-09-24 01:34:41 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-24 01:34:41 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-24 01:34:42 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DfosxzxSC9/ea_profile.json
* 2024-09-24 01:34:47 (390) [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/DfosxzxSC9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-24 01:34:47 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-25 01:33:25 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-25 01:33:25 (9030) [INFO] Script is up to date.
* 2024-09-25 01:33:26 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-25 01:33:26 (2274) [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-09-25 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-25 01:33:27 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-25 01:33:27 (7667) [INFO] 
* 2024-09-25 01:33:32 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-25 01:33:32 (682) [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.

* 2024-09-25 01:33:32 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-25 01:33:32 (7667) [INFO] 
* 2024-09-25 01:33:46 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-25 01:33:46 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-25 01:33:46 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-25 01:33:46 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-25 01:33:46 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-25 01:33:46 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-25 01:33:46 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-25 01:33:46 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-25 01:33:46 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-25 01:33:50 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-25 01:33:50 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-25 01:33:50 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-25 01:33:50 (7667) [INFO] 
* 2024-09-25 01:33:50 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-25 01:33:50 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-25 01:33:50 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-25 01:33:50 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-25 01:33:50 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-25 01:33:50 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-25 01:33:50 (7680) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-25 01:33:50 (7680) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-25 01:33:50 (7680) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-25 01:33:50 (7680) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-25 01:33:50 (7680) [INFO]               : yarn
* 2024-09-25 01:33:50 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-25 01:33:50 (7680) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-25 01:33:50 (7697) [INFO] 
* 2024-09-25 01:33:57 (2005) [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-09-25 01:33:57 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-25 01:33:57 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-25 01:33:58 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2_D1dB4EqK/ea_profile.json
* 2024-09-25 01:34:03 (390) [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/2_D1dB4EqK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-25 01:34:03 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-26 01:33:33 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-26 01:33:33 (9030) [INFO] Script is up to date.
* 2024-09-26 01:33:34 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-26 01:33:34 (2274) [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-09-26 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-26 01:33:34 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-26 01:33:34 (7667) [INFO] 
* 2024-09-26 01:33:39 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-26 01:33:39 (682) [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.

* 2024-09-26 01:33:39 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-26 01:33:39 (7667) [INFO] 
* 2024-09-26 01:33:57 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-26 01:33:57 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-26 01:33:57 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-26 01:33:57 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-26 01:33:57 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-26 01:33:57 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-26 01:33:57 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-26 01:33:57 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-26 01:33:57 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-26 01:34:01 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-26 01:34:01 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-26 01:34:01 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-26 01:34:01 (7667) [INFO] 
* 2024-09-26 01:34:01 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-26 01:34:01 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-26 01:34:01 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-26 01:34:01 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-26 01:34:01 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-26 01:34:01 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-26 01:34:01 (7680) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-26 01:34:01 (7680) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-26 01:34:01 (7680) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-26 01:34:01 (7680) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-26 01:34:01 (7680) [INFO]               : yarn
* 2024-09-26 01:34:01 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-26 01:34:01 (7680) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-26 01:34:01 (7697) [INFO] 
* 2024-09-26 01:34:08 (2005) [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-09-26 01:34:08 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-26 01:34:08 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-26 01:34:09 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u_93fyRBPj/ea_profile.json
* 2024-09-26 01:34:14 (390) [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/u_93fyRBPj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-26 01:34:14 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-28 01:34:03 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-28 01:34:03 (9030) [INFO] Script is up to date.
* 2024-09-28 01:34:04 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-28 01:34:04 (2274) [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-09-28 01:34:05 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-28 01:34:05 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-28 01:34:05 (7667) [INFO] 
* 2024-09-28 01:34:09 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-28 01:34:09 (682) [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.

* 2024-09-28 01:34:09 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-28 01:34:09 (7667) [INFO] 
* 2024-09-28 01:34:22 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-28 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-28 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-28 01:34:22 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-28 01:34:22 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-28 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-28 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-28 01:34:22 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-28 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-28 01:34:26 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-28 01:34:26 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-28 01:34:26 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-28 01:34:26 (7667) [INFO] 
* 2024-09-28 01:34:26 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-28 01:34:27 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-28 01:34:27 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-28 01:34:27 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-28 01:34:27 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-28 01:34:27 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-28 01:34:27 (7680) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-28 01:34:27 (7680) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-28 01:34:27 (7680) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-28 01:34:27 (7680) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-28 01:34:27 (7680) [INFO]               : yarn
* 2024-09-28 01:34:27 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-28 01:34:27 (7680) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-28 01:34:27 (7697) [INFO] 
* 2024-09-28 01:34:32 (2005) [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-09-28 01:34:32 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-28 01:34:32 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-28 01:34:34 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N9w3SpWuLc/ea_profile.json
* 2024-09-28 01:34:38 (390) [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/N9w3SpWuLc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-28 01:34:38 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-29 01:33:59 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-29 01:33:59 (9030) [INFO] Script is up to date.
* 2024-09-29 01:34:00 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-29 01:34:00 (2274) [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-09-29 01:34:01 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-29 01:34:01 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-29 01:34:01 (7667) [INFO] 
* 2024-09-29 01:34:08 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-29 01:34:08 (682) [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.

* 2024-09-29 01:34:08 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-29 01:34:08 (7667) [INFO] 
* 2024-09-29 01:34:18 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-29 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-29 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-29 01:34:18 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-29 01:34:18 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-29 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-29 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-29 01:34:18 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-29 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-29 01:34:23 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-29 01:34:23 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-29 01:34:23 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-29 01:34:23 (7667) [INFO] 
* 2024-09-29 01:34:23 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-29 01:34:23 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-29 01:34:23 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-29 01:34:23 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-29 01:34:23 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-29 01:34:23 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-29 01:34:23 (7680) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-29 01:34:23 (7680) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-29 01:34:23 (7680) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-29 01:34:23 (7680) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-29 01:34:23 (7680) [INFO]               : yarn
* 2024-09-29 01:34:23 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-29 01:34:23 (7680) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-29 01:34:23 (7697) [INFO] 
* 2024-09-29 01:34:31 (2005) [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-09-29 01:34:31 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-29 01:34:31 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-29 01:34:33 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fycyUaDech/ea_profile.json
* 2024-09-29 01:34:38 (390) [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/fycyUaDech/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-29 01:34:38 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-30 01:33:24 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-30 01:33:24 (9030) [INFO] Script is up to date.
* 2024-09-30 01:33:25 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-09-30 01:33:26 (2274) [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-09-30 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-09-30 01:33:26 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-30 01:33:26 (7667) [INFO] 
* 2024-09-30 01:33:30 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-09-30 01:33:30 (682) [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.

* 2024-09-30 01:33:30 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-30 01:33:30 (7667) [INFO] 
* 2024-09-30 01:33:45 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-09-30 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-09-30 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-09-30 01:33:45 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-30 01:33:45 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-09-30 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-09-30 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-09-30 01:33:45 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-09-30 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-09-30 01:33:48 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-30 01:33:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-30 01:33:48 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-30 01:33:48 (7667) [INFO] 
* 2024-09-30 01:33:48 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-30 01:33:49 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-09-30 01:33:49 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-30 01:33:49 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-30 01:33:49 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-09-30 01:33:49 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-30 01:33:49 (7680) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-09-30 01:33:49 (7680) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-09-30 01:33:49 (7680) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-09-30 01:33:49 (7680) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-30 01:33:49 (7680) [INFO]               : yarn
* 2024-09-30 01:33:49 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-30 01:33:49 (7680) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-09-30 01:33:49 (7697) [INFO] 
* 2024-09-30 01:33:54 (2005) [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-09-30 01:33:54 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-09-30 01:33:54 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-30 01:33:55 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pwzbN4WGAU/ea_profile.json
* 2024-09-30 01:33:59 (390) [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/pwzbN4WGAU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-30 01:33:59 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-01 01:33:26 (9008) [INFO] Self-update of script version 54 requested.
* 2024-10-01 01:33:27 (9013) [INFO] Newer version of script found. Downloading.
* 2024-10-01 01:33:27 (9022) [INFO] Script update to version 55 successful.
* 2024-10-01 01:33:28 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-01 01:33:28 (2274) [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-10-01 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-01 01:33:28 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-01 01:33:28 (7668) [INFO] 
* 2024-10-01 01:33:32 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-01 01:33:32 (682) [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.

* 2024-10-01 01:33:32 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-01 01:33:32 (7668) [INFO] 
* 2024-10-01 01:33:48 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-01 01:33:48 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-01 01:33:48 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-01 01:33:48 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-01 01:33:48 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-01 01:33:48 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-01 01:33:48 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-01 01:33:48 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-01 01:33:48 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-01 01:33:53 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-01 01:33:53 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-01 01:33:53 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-01 01:33:53 (7668) [INFO] 
* 2024-10-01 01:33:53 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-01 01:33:53 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-01 01:33:53 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-01 01:33:53 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-01 01:33:53 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-01 01:33:53 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-01 01:33:53 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-01 01:33:53 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-01 01:33:53 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-01 01:33:53 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-01 01:33:53 (7681) [INFO]               : yarn
* 2024-10-01 01:33:53 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-01 01:33:53 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-01 01:33:53 (7698) [INFO] 
* 2024-10-01 01:34:00 (2005) [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-10-01 01:34:00 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-01 01:34:00 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-01 01:34:01 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/t9XGuGcru7/ea_profile.json
* 2024-10-01 01:34:07 (390) [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/t9XGuGcru7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-01 01:34:07 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-03 01:34:02 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-03 01:34:02 (9031) [INFO] Script is up to date.
* 2024-10-03 01:34:03 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-03 01:34:03 (2274) [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-10-03 01:34:06 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-03 01:34:06 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-03 01:34:06 (7668) [INFO] 
* 2024-10-03 01:34:10 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-03 01:34:10 (682) [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.

* 2024-10-03 01:34:10 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-03 01:34:10 (7668) [INFO] 
* 2024-10-03 01:34:27 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-03 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-03 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-03 01:34:27 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-03 01:34:27 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-03 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-03 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-03 01:34:27 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-03 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-03 01:34:33 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-03 01:34:33 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-03 01:34:33 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-03 01:34:33 (7668) [INFO] 
* 2024-10-03 01:34:33 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-03 01:34:33 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-03 01:34:33 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-03 01:34:33 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-03 01:34:33 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-03 01:34:33 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-03 01:34:33 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-03 01:34:33 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-03 01:34:33 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-03 01:34:33 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-03 01:34:33 (7681) [INFO]               : yarn
* 2024-10-03 01:34:33 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-03 01:34:33 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-03 01:34:33 (7698) [INFO] 
* 2024-10-03 01:34:40 (2005) [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-10-03 01:34:40 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-03 01:34:40 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-03 01:34:41 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/z6KrTPZSeg/ea_profile.json
* 2024-10-03 01:34:48 (390) [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/z6KrTPZSeg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-03 01:34:48 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-04 01:33:25 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-04 01:33:25 (9031) [INFO] Script is up to date.
* 2024-10-04 01:33:26 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-04 01:33:26 (2274) [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-10-04 01:33:26 (230) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2024-10-04 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-04 01:33:26 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-04 01:33:26 (7668) [INFO] 
* 2024-10-04 01:33:32 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-04 01:33:32 (682) [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.

* 2024-10-04 01:33:32 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-04 01:33:32 (7668) [INFO] 
* 2024-10-04 01:33:43 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-04 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-04 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-04 01:33:43 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-04 01:33:43 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-04 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-04 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-04 01:33:43 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-04 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-04 01:33:47 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-04 01:33:47 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-04 01:33:47 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-04 01:33:47 (7668) [INFO] 
* 2024-10-04 01:33:47 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-04 01:33:47 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-04 01:33:47 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-04 01:33:47 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-04 01:33:47 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-04 01:33:47 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-04 01:33:47 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-04 01:33:47 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-04 01:33:47 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-04 01:33:47 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-04 01:33:47 (7681) [INFO]               : yarn
* 2024-10-04 01:33:47 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-04 01:33:47 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-04 01:33:47 (7698) [INFO] 
* 2024-10-04 01:33:51 (2005) [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-10-04 01:33:51 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-04 01:33:52 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-04 01:33:53 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/60yYvusW1N/ea_profile.json
* 2024-10-04 01:33:57 (390) [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/60yYvusW1N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-04 01:33:57 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-05 01:34:04 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-05 01:34:04 (9031) [INFO] Script is up to date.
* 2024-10-05 01:34:05 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-05 01:34:05 (2274) [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-10-05 01:34:09 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-05 01:34:09 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-05 01:34:09 (7668) [INFO] 
* 2024-10-05 01:34:17 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-05 01:34:17 (682) [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.

* 2024-10-05 01:34:17 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-05 01:34:17 (7668) [INFO] 
* 2024-10-05 01:34:22 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-05 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-05 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-05 01:34:22 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-05 01:34:22 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-05 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-05 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-05 01:34:22 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-05 01:34:22 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-05 01:34:26 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-05 01:34:26 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-05 01:34:26 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-05 01:34:26 (7668) [INFO] 
* 2024-10-05 01:34:26 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-05 01:34:26 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-05 01:34:26 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-05 01:34:26 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-05 01:34:26 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-05 01:34:26 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-05 01:34:26 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-05 01:34:26 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-05 01:34:26 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-05 01:34:26 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-05 01:34:26 (7681) [INFO]               : yarn
* 2024-10-05 01:34:26 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-05 01:34:26 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-05 01:34:26 (7698) [INFO] 
* 2024-10-05 01:34:31 (2005) [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-10-05 01:34:31 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-05 01:34:31 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-05 01:34:33 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MKpXhcqeVz/ea_profile.json
* 2024-10-05 01:34:36 (390) [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/MKpXhcqeVz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-05 01:34:36 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-06 01:33:54 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-06 01:33:54 (9031) [INFO] Script is up to date.
* 2024-10-06 01:33:55 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-06 01:33:55 (2274) [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-10-06 01:33:55 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-06 01:33:55 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-06 01:33:55 (7668) [INFO] 
* 2024-10-06 01:33:59 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-06 01:33:59 (682) [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.

* 2024-10-06 01:33:59 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-06 01:33:59 (7668) [INFO] 
* 2024-10-06 01:34:18 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-06 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-06 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-06 01:34:18 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-06 01:34:18 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-06 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-06 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-06 01:34:18 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-06 01:34:18 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-06 01:34:22 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-06 01:34:22 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-06 01:34:22 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-06 01:34:22 (7668) [INFO] 
* 2024-10-06 01:34:22 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-06 01:34:22 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-06 01:34:22 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-06 01:34:22 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-06 01:34:22 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-06 01:34:22 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-06 01:34:22 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-06 01:34:22 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-06 01:34:22 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-06 01:34:22 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-06 01:34:22 (7681) [INFO]               : yarn
* 2024-10-06 01:34:22 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-06 01:34:22 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-06 01:34:22 (7698) [INFO] 
* 2024-10-06 01:34:30 (2005) [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-10-06 01:34:30 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-06 01:34:30 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-06 01:34:31 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vecYPw_Uxe/ea_profile.json
* 2024-10-06 01:34:35 (390) [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/vecYPw_Uxe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-06 01:34:35 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-07 01:33:26 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-07 01:33:26 (9031) [INFO] Script is up to date.
* 2024-10-07 01:33:27 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-07 01:33:27 (2274) [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-10-07 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-07 01:33:27 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-07 01:33:27 (7668) [INFO] 
* 2024-10-07 01:33:31 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-07 01:33:31 (682) [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.

* 2024-10-07 01:33:31 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-07 01:33:31 (7668) [INFO] 
* 2024-10-07 01:33:49 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-07 01:33:49 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-07 01:33:49 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-07 01:33:49 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-07 01:33:49 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-07 01:33:49 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-07 01:33:49 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-07 01:33:49 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-07 01:33:49 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-07 01:33:54 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-07 01:33:54 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-07 01:33:54 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-07 01:33:54 (7668) [INFO] 
* 2024-10-07 01:33:54 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-07 01:33:54 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-07 01:33:54 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-07 01:33:54 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-07 01:33:54 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-07 01:33:54 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-07 01:33:54 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-07 01:33:54 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-07 01:33:54 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-07 01:33:54 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-07 01:33:54 (7681) [INFO]               : yarn
* 2024-10-07 01:33:54 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-07 01:33:54 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-07 01:33:54 (7698) [INFO] 
* 2024-10-07 01:34:00 (2005) [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-10-07 01:34:00 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-07 01:34:00 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-07 01:34:01 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QFOdbM5g6h/ea_profile.json
* 2024-10-07 01:34:07 (390) [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/QFOdbM5g6h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-07 01:34:07 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-08 01:33:37 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-08 01:33:37 (9031) [INFO] Script is up to date.
* 2024-10-08 01:33:38 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-08 01:33:38 (2274) [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-10-08 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-08 01:33:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-08 01:33:38 (7668) [INFO] 
* 2024-10-08 01:33:42 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-08 01:33:42 (682) [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.

* 2024-10-08 01:33:42 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-08 01:33:42 (7668) [INFO] 
* 2024-10-08 01:33:52 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-08 01:33:52 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-08 01:33:52 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-08 01:33:52 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-08 01:33:52 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-08 01:33:52 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-08 01:33:52 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-08 01:33:52 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-08 01:33:52 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-08 01:33:57 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-08 01:33:57 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-08 01:33:57 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-08 01:33:57 (7668) [INFO] 
* 2024-10-08 01:33:57 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-08 01:33:57 (7681) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 1029378.
* 2024-10-08 01:33:57 (7681) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-10-08 01:33:57 (7681) [INFO]   The other application is: yum
* 2024-10-08 01:33:57 (7681) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-10-08 01:33:57 (7681) [INFO]     Started: Tue Oct  8 01:33:46 2024 - 00:11 ago
* 2024-10-08 01:33:57 (7681) [INFO]     State  : Sleeping, pid: 1029378
* 2024-10-08 01:33:59 (7681) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-10-08 01:33:59 (7681) [INFO]   The other application is: yum
* 2024-10-08 01:33:59 (7681) [INFO]     Memory :  39 M RSS (332 MB VSZ)
* 2024-10-08 01:33:59 (7681) [INFO]     Started: Tue Oct  8 01:33:46 2024 - 00:13 ago
* 2024-10-08 01:33:59 (7681) [INFO]     State  : Sleeping, pid: 1029378
* 2024-10-08 01:34:01 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-08 01:34:01 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-08 01:34:01 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-08 01:34:01 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-08 01:34:01 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-08 01:34:01 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-08 01:34:01 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-08 01:34:01 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-08 01:34:01 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-08 01:34:01 (7681) [INFO]               : yarn
* 2024-10-08 01:34:01 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-08 01:34:01 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-08 01:34:01 (7698) [INFO] 
* 2024-10-08 01:34:08 (2005) [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-10-08 01:34:08 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-08 01:34:08 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-08 01:34:09 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9vqlxozqAd/ea_profile.json
* 2024-10-08 01:34:13 (390) [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/9vqlxozqAd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-08 01:34:13 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-09 01:33:34 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-09 01:33:34 (9031) [INFO] Script is up to date.
* 2024-10-09 01:33:35 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-09 01:33:35 (2274) [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-10-09 01:33:35 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-09 01:33:35 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-09 01:33:35 (7668) [INFO] 
* 2024-10-09 01:33:40 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-09 01:33:40 (682) [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.

* 2024-10-09 01:33:40 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-09 01:33:40 (7668) [INFO] 
* 2024-10-09 01:33:51 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-09 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-09 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-09 01:33:51 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-09 01:33:51 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-09 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-09 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-09 01:33:51 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-09 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-09 01:33:56 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-09 01:33:56 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-09 01:33:56 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-09 01:33:56 (7668) [INFO] 
* 2024-10-09 01:33:56 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-09 01:33:56 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-09 01:33:56 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-09 01:33:56 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-09 01:33:56 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-09 01:33:56 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-09 01:33:56 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-09 01:33:56 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-09 01:33:56 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-09 01:33:56 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-09 01:33:56 (7681) [INFO]               : yarn
* 2024-10-09 01:33:56 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-09 01:33:56 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-09 01:33:56 (7698) [INFO] 
* 2024-10-09 01:34:02 (2005) [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-10-09 01:34:02 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-09 01:34:02 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-09 01:34:04 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DCQ6ONmKlG/ea_profile.json
* 2024-10-09 01:34:09 (390) [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/DCQ6ONmKlG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-09 01:34:09 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-10 01:33:27 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-10 01:33:27 (9031) [INFO] Script is up to date.
* 2024-10-10 01:33:28 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-10 01:33:28 (2274) [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-10-10 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-10 01:33:28 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-10 01:33:28 (7668) [INFO] 
* 2024-10-10 01:33:32 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-10 01:33:32 (682) [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.

* 2024-10-10 01:33:32 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-10 01:33:32 (7668) [INFO] 
* 2024-10-10 01:33:41 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-10 01:33:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-10 01:33:41 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-10 01:33:41 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-10 01:33:41 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-10 01:33:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-10 01:33:41 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-10 01:33:41 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-10 01:33:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-10 01:33:46 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-10 01:33:46 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-10 01:33:46 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-10 01:33:46 (7668) [INFO] 
* 2024-10-10 01:33:46 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-10 01:33:46 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-10 01:33:46 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-10 01:33:46 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-10 01:33:46 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-10 01:33:46 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-10 01:33:46 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-10 01:33:46 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-10 01:33:46 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-10 01:33:46 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-10 01:33:46 (7681) [INFO]               : yarn
* 2024-10-10 01:33:46 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-10 01:33:46 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-10 01:33:46 (7698) [INFO] 
* 2024-10-10 01:33:57 (2005) [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-10-10 01:33:57 (2006) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 771832.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (328 MB VSZ)
    Started: Thu Oct 10 01:33:35 2024 - 00:12 ago
    State  : Running, pid: 771832
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (2.8 GB VSZ)
    Started: Thu Oct 10 01:33:35 2024 - 00:14 ago
    State  : Sleeping, pid: 771832
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Thu Oct 10 01:33:35 2024 - 00:16 ago
    State  : Sleeping, pid: 771832
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-10 01:33:57 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-10 01:33:58 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bCKAW5V7vX/ea_profile.json
* 2024-10-10 01:34:03 (390) [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/bCKAW5V7vX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-10 01:34:03 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-11 01:33:27 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-11 01:33:28 (9031) [INFO] Script is up to date.
* 2024-10-11 01:33:29 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-11 01:33:29 (2274) [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-10-11 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-11 01:33:29 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-11 01:33:29 (7668) [INFO] 
* 2024-10-11 01:33:33 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-11 01:33:33 (682) [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.

* 2024-10-11 01:33:33 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-11 01:33:33 (7668) [INFO] 
* 2024-10-11 01:33:59 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-11 01:33:59 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-11 01:33:59 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-11 01:33:59 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-11 01:33:59 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-11 01:33:59 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-11 01:33:59 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-11 01:33:59 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-11 01:33:59 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-11 01:34:06 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-11 01:34:06 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-11 01:34:06 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-11 01:34:06 (7668) [INFO] 
* 2024-10-11 01:34:06 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-11 01:34:07 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-11 01:34:07 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-11 01:34:07 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-11 01:34:07 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-11 01:34:07 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-11 01:34:07 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-11 01:34:07 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-11 01:34:07 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-11 01:34:07 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-11 01:34:07 (7681) [INFO]               : yarn
* 2024-10-11 01:34:07 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-11 01:34:07 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-11 01:34:07 (7698) [INFO] 
* 2024-10-11 01:34:16 (2005) [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-10-11 01:34:16 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-11 01:34:16 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-11 01:34:17 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v5Rf6Ayppg/ea_profile.json
* 2024-10-11 01:34:22 (390) [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/v5Rf6Ayppg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-11 01:34:22 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-12 01:34:09 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-12 01:34:09 (9031) [INFO] Script is up to date.
* 2024-10-12 01:34:10 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-12 01:34:10 (2274) [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-10-12 01:34:10 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-12 01:34:10 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-12 01:34:10 (7668) [INFO] 
* 2024-10-12 01:34:15 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-12 01:34:15 (682) [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.

* 2024-10-12 01:34:15 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-12 01:34:15 (7668) [INFO] 
* 2024-10-12 01:34:30 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-12 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-12 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-12 01:34:30 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-12 01:34:30 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-12 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-12 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-12 01:34:30 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-12 01:34:30 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-12 01:34:34 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-12 01:34:34 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-12 01:34:34 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-12 01:34:34 (7668) [INFO] 
* 2024-10-12 01:34:34 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-12 01:34:35 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-12 01:34:35 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-12 01:34:35 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-12 01:34:35 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-12 01:34:35 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-12 01:34:35 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-12 01:34:35 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-12 01:34:35 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-12 01:34:35 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-12 01:34:35 (7681) [INFO]               : yarn
* 2024-10-12 01:34:35 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-12 01:34:35 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-12 01:34:35 (7698) [INFO] 
* 2024-10-12 01:34:40 (2005) [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-10-12 01:34:40 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-12 01:34:40 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-12 01:34:41 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MtXXTsKd1b/ea_profile.json
* 2024-10-12 01:34:45 (390) [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/MtXXTsKd1b/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-12 01:34:45 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-13 01:34:07 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-13 01:34:07 (9031) [INFO] Script is up to date.
* 2024-10-13 01:34:08 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-13 01:34:08 (2274) [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-10-13 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-13 01:34:08 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-13 01:34:08 (7668) [INFO] 
* 2024-10-13 01:34:13 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-13 01:34:13 (682) [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.

* 2024-10-13 01:34:13 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-13 01:34:13 (7668) [INFO] 
* 2024-10-13 01:34:27 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-13 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-13 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-13 01:34:27 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-13 01:34:27 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-13 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-13 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-13 01:34:27 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-13 01:34:27 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-13 01:34:36 (1995) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 902572.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  37 M RSS (331 MB VSZ)
    Started: Sun Oct 13 01:34:20 2024 - 00:08 ago
    State  : Sleeping, pid: 902572
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Sun Oct 13 01:34:20 2024 - 00:10 ago
    State  : Sleeping, pid: 902572
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-13 01:34:36 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-13 01:34:36 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-13 01:34:36 (7668) [INFO] 
* 2024-10-13 01:34:36 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-13 01:34:36 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-13 01:34:36 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-13 01:34:36 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-13 01:34:36 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-13 01:34:36 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-13 01:34:36 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-13 01:34:36 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-13 01:34:36 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-13 01:34:36 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-13 01:34:36 (7681) [INFO]               : yarn
* 2024-10-13 01:34:36 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-13 01:34:36 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-13 01:34:36 (7698) [INFO] 
* 2024-10-13 01:34:43 (2005) [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-10-13 01:34:43 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-13 01:34:43 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-13 01:34:44 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CDdXEuSdlN/ea_profile.json
* 2024-10-13 01:34:48 (390) [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/CDdXEuSdlN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-13 01:34:48 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-14 01:33:27 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-14 01:33:27 (9031) [INFO] Script is up to date.
* 2024-10-14 01:33:28 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-14 01:33:28 (2274) [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-10-14 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-14 01:33:28 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-14 01:33:28 (7668) [INFO] 
* 2024-10-14 01:33:32 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-14 01:33:32 (682) [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.

* 2024-10-14 01:33:32 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-14 01:33:32 (7668) [INFO] 
* 2024-10-14 01:33:47 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-14 01:33:47 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-14 01:33:47 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-14 01:33:47 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-14 01:33:47 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-14 01:33:47 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-14 01:33:47 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-14 01:33:47 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-14 01:33:47 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-14 01:33:52 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-14 01:33:52 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-14 01:33:52 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-14 01:33:52 (7668) [INFO] 
* 2024-10-14 01:33:52 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-14 01:33:52 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-14 01:33:52 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-14 01:33:52 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-14 01:33:52 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-14 01:33:52 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-14 01:33:52 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-14 01:33:52 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-14 01:33:52 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-14 01:33:52 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-14 01:33:52 (7681) [INFO]               : yarn
* 2024-10-14 01:33:52 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-14 01:33:52 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-14 01:33:52 (7698) [INFO] 
* 2024-10-14 01:33:58 (2005) [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-10-14 01:33:58 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-14 01:33:58 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-14 01:34:00 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wpAnNl8kwX/ea_profile.json
* 2024-10-14 01:34:05 (390) [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/wpAnNl8kwX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-14 01:34:05 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-15 01:33:37 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-15 01:33:37 (9031) [INFO] Script is up to date.
* 2024-10-15 01:33:38 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-15 01:33:38 (2274) [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-10-15 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-15 01:33:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-15 01:33:38 (7668) [INFO] 
* 2024-10-15 01:33:43 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-15 01:33:43 (682) [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.

* 2024-10-15 01:33:43 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-15 01:33:43 (7668) [INFO] 
* 2024-10-15 01:34:00 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-15 01:34:00 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-15 01:34:00 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-15 01:34:00 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-15 01:34:00 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-15 01:34:00 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-15 01:34:00 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-15 01:34:00 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-15 01:34:00 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-15 01:34:05 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-15 01:34:05 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-15 01:34:05 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-15 01:34:05 (7668) [INFO] 
* 2024-10-15 01:34:05 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-15 01:34:05 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-15 01:34:05 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-15 01:34:05 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-15 01:34:05 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-15 01:34:05 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-15 01:34:05 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-15 01:34:05 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-15 01:34:05 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-15 01:34:05 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-15 01:34:05 (7681) [INFO]               : yarn
* 2024-10-15 01:34:05 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-15 01:34:05 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-15 01:34:05 (7698) [INFO] 
* 2024-10-15 01:34:12 (2005) [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-10-15 01:34:12 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-15 01:34:12 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-15 01:34:14 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L9QH1P9j3t/ea_profile.json
* 2024-10-15 01:34:19 (390) [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/L9QH1P9j3t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-15 01:34:19 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-16 01:34:13 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-16 01:34:13 (9031) [INFO] Script is up to date.
* 2024-10-16 01:34:14 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-16 01:34:14 (2274) [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-10-16 01:34:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-16 01:34:14 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-16 01:34:14 (7668) [INFO] 
* 2024-10-16 01:34:18 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-16 01:34:18 (682) [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.

* 2024-10-16 01:34:18 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-16 01:34:18 (7668) [INFO] 
* 2024-10-16 01:34:29 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-16 01:34:29 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-16 01:34:29 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-16 01:34:29 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-16 01:34:29 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-16 01:34:29 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-16 01:34:29 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-16 01:34:29 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-16 01:34:29 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-16 01:34:46 (1995) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 959428.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Wed Oct 16 01:34:18 2024 - 00:11 ago
    State  : Sleeping, pid: 959428
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Wed Oct 16 01:34:18 2024 - 00:13 ago
    State  : Sleeping, pid: 959428
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (333 MB VSZ)
    Started: Wed Oct 16 01:34:18 2024 - 00:15 ago
    State  : Sleeping, pid: 959428
Existing lock /var/run/yum.pid: another copy is running as pid 959920.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Wed Oct 16 01:34:34 2024 - 00:01 ago
    State  : Sleeping, pid: 959920
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (332 MB VSZ)
    Started: Wed Oct 16 01:34:34 2024 - 00:03 ago
    State  : Sleeping, pid: 959920
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (334 MB VSZ)
    Started: Wed Oct 16 01:34:34 2024 - 00:05 ago
    State  : Sleeping, pid: 959920
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-16 01:34:46 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-16 01:34:46 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-16 01:34:46 (7668) [INFO] 
* 2024-10-16 01:34:46 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-16 01:34:46 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-16 01:34:46 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-16 01:34:46 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-16 01:34:46 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-16 01:34:46 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-16 01:34:46 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-16 01:34:46 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-16 01:34:46 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-16 01:34:46 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-16 01:34:46 (7681) [INFO]               : yarn
* 2024-10-16 01:34:46 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-16 01:34:46 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-16 01:34:46 (7698) [INFO] 
* 2024-10-16 01:34:53 (2005) [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-10-16 01:34:53 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-16 01:34:54 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-16 01:34:55 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dhOnagSL2N/ea_profile.json
* 2024-10-16 01:35:01 (390) [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/dhOnagSL2N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-16 01:35:01 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-17 01:33:26 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-17 01:33:26 (9031) [INFO] Script is up to date.
* 2024-10-17 01:33:27 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-17 01:33:27 (2274) [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-10-17 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-17 01:33:27 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-17 01:33:27 (7668) [INFO] 
* 2024-10-17 01:33:31 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-17 01:33:31 (682) [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.

* 2024-10-17 01:33:31 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-17 01:33:31 (7668) [INFO] 
* 2024-10-17 01:34:10 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-17 01:34:10 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-17 01:34:10 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-17 01:34:10 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-17 01:34:10 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-17 01:34:10 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-17 01:34:10 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-17 01:34:10 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-17 01:34:10 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-17 01:34:19 (1995) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 394736.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Thu Oct 17 01:34:06 2024 - 00:05 ago
    State  : Sleeping, pid: 394736
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  38 M RSS (333 MB VSZ)
    Started: Thu Oct 17 01:34:06 2024 - 00:07 ago
    State  : Running, pid: 394736
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-17 01:34:19 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-17 01:34:19 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-17 01:34:19 (7668) [INFO] 
* 2024-10-17 01:34:19 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-17 01:34:19 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-17 01:34:19 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-17 01:34:19 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-17 01:34:19 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-17 01:34:19 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-17 01:34:19 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-17 01:34:19 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-17 01:34:19 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-17 01:34:19 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-17 01:34:19 (7681) [INFO]               : yarn
* 2024-10-17 01:34:19 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-17 01:34:19 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-17 01:34:19 (7698) [INFO] 
* 2024-10-17 01:34:24 (2005) [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-10-17 01:34:24 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-17 01:34:24 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-17 01:34:25 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3vXD5caw2d/ea_profile.json
* 2024-10-17 01:34:30 (390) [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/3vXD5caw2d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-17 01:34:30 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-18 01:34:13 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-18 01:34:13 (9031) [INFO] Script is up to date.
* 2024-10-18 01:34:14 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-18 01:34:14 (2274) [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-10-18 01:34:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-18 01:34:14 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-18 01:34:14 (7668) [INFO] 
* 2024-10-18 01:34:19 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-18 01:34:19 (682) [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.

* 2024-10-18 01:34:19 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-18 01:34:19 (7668) [INFO] 
* 2024-10-18 01:34:41 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-18 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-18 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-18 01:34:41 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-18 01:34:41 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-18 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-18 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-18 01:34:41 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-18 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-18 01:34:45 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-18 01:34:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-18 01:34:45 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-18 01:34:45 (7668) [INFO] 
* 2024-10-18 01:34:45 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-18 01:34:45 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-18 01:34:45 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-18 01:34:45 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-18 01:34:45 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-18 01:34:45 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-18 01:34:45 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-18 01:34:45 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-18 01:34:45 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-18 01:34:45 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-18 01:34:45 (7681) [INFO]               : yarn
* 2024-10-18 01:34:45 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-18 01:34:45 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-18 01:34:45 (7698) [INFO] 
* 2024-10-18 01:34:51 (2005) [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-10-18 01:34:51 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-18 01:34:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-18 01:34:52 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cbqyW8pJ6a/ea_profile.json
* 2024-10-18 01:34:56 (390) [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/cbqyW8pJ6a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-18 01:34:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-19 01:34:16 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-19 01:34:16 (9031) [INFO] Script is up to date.
* 2024-10-19 01:34:17 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-19 01:34:18 (2274) [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-10-19 01:34:18 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-19 01:34:18 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-19 01:34:18 (7668) [INFO] 
* 2024-10-19 01:34:22 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-19 01:34:22 (682) [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.

* 2024-10-19 01:34:22 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-19 01:34:22 (7668) [INFO] 
* 2024-10-19 01:34:41 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-19 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-19 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-19 01:34:41 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-19 01:34:41 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-19 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-19 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-19 01:34:41 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-19 01:34:41 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-19 01:34:45 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-19 01:34:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-19 01:34:45 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-19 01:34:45 (7668) [INFO] 
* 2024-10-19 01:34:46 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-19 01:34:46 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-19 01:34:46 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-19 01:34:46 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-19 01:34:46 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-19 01:34:46 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-19 01:34:46 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-19 01:34:46 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-19 01:34:46 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-19 01:34:46 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-19 01:34:46 (7681) [INFO]               : yarn
* 2024-10-19 01:34:46 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-19 01:34:46 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-19 01:34:46 (7698) [INFO] 
* 2024-10-19 01:34:51 (2005) [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-10-19 01:34:51 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-19 01:34:52 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-19 01:34:53 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TVTIEN3Dno/ea_profile.json
* 2024-10-19 01:34:57 (390) [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/TVTIEN3Dno/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-19 01:34:57 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-20 01:33:57 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-20 01:33:57 (9031) [INFO] Script is up to date.
* 2024-10-20 01:33:58 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-20 01:33:58 (2274) [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-10-20 01:33:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-20 01:33:58 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-20 01:33:58 (7668) [INFO] 
* 2024-10-20 01:34:03 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-20 01:34:03 (682) [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.

* 2024-10-20 01:34:03 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-20 01:34:03 (7668) [INFO] 
* 2024-10-20 01:34:21 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-20 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-20 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-20 01:34:21 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-20 01:34:21 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-20 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-20 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-20 01:34:21 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-20 01:34:21 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-20 01:34:26 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-20 01:34:26 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-20 01:34:26 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-20 01:34:26 (7668) [INFO] 
* 2024-10-20 01:34:26 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-20 01:34:26 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-20 01:34:26 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-20 01:34:26 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-20 01:34:26 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-20 01:34:26 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-20 01:34:26 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-20 01:34:26 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-20 01:34:26 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-20 01:34:26 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-20 01:34:26 (7681) [INFO]               : yarn
* 2024-10-20 01:34:26 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-20 01:34:26 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-20 01:34:26 (7698) [INFO] 
* 2024-10-20 01:34:33 (2005) [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-10-20 01:34:33 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-20 01:34:33 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-20 01:34:34 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iFVvl0INsS/ea_profile.json
* 2024-10-20 01:34:40 (390) [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/iFVvl0INsS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-20 01:34:40 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-21 01:33:25 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-21 01:33:25 (9031) [INFO] Script is up to date.
* 2024-10-21 01:33:26 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-21 01:33:26 (2274) [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-10-21 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-21 01:33:27 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-21 01:33:27 (7668) [INFO] 
* 2024-10-21 01:33:31 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-21 01:33:31 (682) [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.

* 2024-10-21 01:33:31 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-21 01:33:31 (7668) [INFO] 
* 2024-10-21 01:33:43 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-21 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-21 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-21 01:33:43 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-21 01:33:43 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-21 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-21 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-21 01:33:43 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-21 01:33:43 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-21 01:33:49 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-21 01:33:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-21 01:33:49 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-21 01:33:49 (7668) [INFO] 
* 2024-10-21 01:33:49 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-21 01:33:49 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-21 01:33:49 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-21 01:33:49 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-21 01:33:49 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-21 01:33:49 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-21 01:33:49 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-21 01:33:49 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-21 01:33:49 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-21 01:33:49 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-21 01:33:49 (7681) [INFO]               : yarn
* 2024-10-21 01:33:49 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-21 01:33:49 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-21 01:33:49 (7698) [INFO] 
* 2024-10-21 01:33:55 (2005) [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-10-21 01:33:55 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-21 01:33:55 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-21 01:33:56 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wXIw7Ju7ye/ea_profile.json
* 2024-10-21 01:34:00 (390) [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/wXIw7Ju7ye/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-21 01:34:00 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-22 01:33:28 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-22 01:33:28 (9031) [INFO] Script is up to date.
* 2024-10-22 01:33:29 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-22 01:33:29 (2274) [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-10-22 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-22 01:33:29 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-22 01:33:29 (7668) [INFO] 
* 2024-10-22 01:33:33 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-22 01:33:33 (682) [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.

* 2024-10-22 01:33:33 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-22 01:33:33 (7668) [INFO] 
* 2024-10-22 01:33:51 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-22 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-22 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-22 01:33:51 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-22 01:33:51 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-22 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-22 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-22 01:33:51 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-22 01:33:51 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-22 01:33:56 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-22 01:33:56 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-22 01:33:56 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-22 01:33:56 (7668) [INFO] 
* 2024-10-22 01:33:56 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-22 01:33:57 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-22 01:33:57 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-22 01:33:57 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-22 01:33:57 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-22 01:33:57 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-22 01:33:57 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-22 01:33:57 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-22 01:33:57 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-22 01:33:57 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-22 01:33:57 (7681) [INFO]               : yarn
* 2024-10-22 01:33:57 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-22 01:33:57 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-22 01:33:57 (7698) [INFO] 
* 2024-10-22 01:34:05 (2005) [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-10-22 01:34:05 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-22 01:34:05 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-22 01:34:07 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AQ393wwQdO/ea_profile.json
* 2024-10-22 01:34:10 (390) [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/AQ393wwQdO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-22 01:34:10 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-23 01:33:37 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-23 01:33:37 (9031) [INFO] Script is up to date.
* 2024-10-23 01:33:38 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-23 01:33:39 (2274) [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-10-23 01:33:39 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-23 01:33:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-23 01:33:39 (7668) [INFO] 
* 2024-10-23 01:33:45 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-23 01:33:45 (682) [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.

* 2024-10-23 01:33:45 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-23 01:33:45 (7668) [INFO] 
* 2024-10-23 01:33:56 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-23 01:33:56 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-23 01:33:56 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-23 01:33:56 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-23 01:33:56 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-23 01:33:56 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-23 01:33:56 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-23 01:33:56 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-23 01:33:56 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-23 01:34:01 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-23 01:34:01 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-23 01:34:01 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-23 01:34:01 (7668) [INFO] 
* 2024-10-23 01:34:01 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-23 01:34:02 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-23 01:34:02 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-23 01:34:02 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-23 01:34:02 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-23 01:34:02 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-23 01:34:02 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-23 01:34:02 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-23 01:34:02 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-23 01:34:02 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-23 01:34:02 (7681) [INFO]               : yarn
* 2024-10-23 01:34:02 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-23 01:34:02 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-23 01:34:02 (7698) [INFO] 
* 2024-10-23 01:34:09 (2005) [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-10-23 01:34:09 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-23 01:34:10 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-23 01:34:11 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3Oqe5HW7a1/ea_profile.json
* 2024-10-23 01:34:17 (390) [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/3Oqe5HW7a1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-23 01:34:17 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-24 01:33:23 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-24 01:33:23 (9031) [INFO] Script is up to date.
* 2024-10-24 01:33:25 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-24 01:33:25 (2274) [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-10-24 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-24 01:33:25 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-24 01:33:25 (7668) [INFO] 
* 2024-10-24 01:33:29 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-24 01:33:29 (682) [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.

* 2024-10-24 01:33:29 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-24 01:33:29 (7668) [INFO] 
* 2024-10-24 01:33:45 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-24 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-24 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-24 01:33:45 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-24 01:33:45 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-24 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-24 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-24 01:33:45 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-24 01:33:45 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-24 01:33:49 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-24 01:33:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-24 01:33:49 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-24 01:33:49 (7668) [INFO] 
* 2024-10-24 01:33:49 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-24 01:33:49 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-24 01:33:49 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-24 01:33:49 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-24 01:33:49 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-24 01:33:49 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-24 01:33:49 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-24 01:33:49 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-24 01:33:49 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-24 01:33:49 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-24 01:33:49 (7681) [INFO]               : yarn
* 2024-10-24 01:33:49 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-24 01:33:49 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-24 01:33:49 (7698) [INFO] 
* 2024-10-24 01:33:57 (2005) [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-10-24 01:33:57 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-24 01:33:57 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-24 01:33:59 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VIxwZjfI2o/ea_profile.json
* 2024-10-24 01:34:04 (390) [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/VIxwZjfI2o/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-24 01:34:04 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-25 01:34:04 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-25 01:34:04 (9031) [INFO] Script is up to date.
* 2024-10-25 01:34:05 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-25 01:34:05 (2274) [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-10-25 01:34:09 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-25 01:34:09 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-25 01:34:09 (7668) [INFO] 
* 2024-10-25 01:34:13 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-25 01:34:13 (682) [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.

* 2024-10-25 01:34:13 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-25 01:34:13 (7668) [INFO] 
* 2024-10-25 01:34:23 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-25 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-25 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-25 01:34:23 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-25 01:34:23 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-25 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-25 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-25 01:34:23 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-25 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-25 01:34:28 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-25 01:34:28 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-25 01:34:28 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-25 01:34:28 (7668) [INFO] 
* 2024-10-25 01:34:28 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-25 01:34:28 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-25 01:34:28 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-25 01:34:28 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-25 01:34:28 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-25 01:34:28 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-25 01:34:28 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-25 01:34:28 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-25 01:34:28 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-25 01:34:28 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-25 01:34:28 (7681) [INFO]               : yarn
* 2024-10-25 01:34:28 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-25 01:34:28 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-25 01:34:28 (7698) [INFO] 
* 2024-10-25 01:34:36 (2005) [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-10-25 01:34:36 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-25 01:34:36 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-25 01:34:37 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IwcZwpaHL6/ea_profile.json
* 2024-10-25 01:34:41 (390) [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/IwcZwpaHL6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-25 01:34:41 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-26 01:34:06 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-26 01:34:06 (9031) [INFO] Script is up to date.
* 2024-10-26 01:34:07 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-26 01:34:07 (2274) [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-10-26 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-26 01:34:08 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-26 01:34:08 (7668) [INFO] 
* 2024-10-26 01:34:12 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-26 01:34:12 (682) [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.

* 2024-10-26 01:34:12 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-26 01:34:12 (7668) [INFO] 
* 2024-10-26 01:34:23 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-26 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-26 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-26 01:34:23 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-26 01:34:23 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-26 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-26 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-26 01:34:23 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-26 01:34:23 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-26 01:34:28 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-26 01:34:28 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-26 01:34:28 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-26 01:34:28 (7668) [INFO] 
* 2024-10-26 01:34:28 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-26 01:34:28 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-26 01:34:28 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-26 01:34:28 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-26 01:34:28 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-26 01:34:28 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-26 01:34:28 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-26 01:34:28 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-26 01:34:28 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-26 01:34:28 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-26 01:34:28 (7681) [INFO]               : yarn
* 2024-10-26 01:34:28 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-26 01:34:28 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-26 01:34:28 (7698) [INFO] 
* 2024-10-26 01:34:38 (2005) [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-10-26 01:34:38 (2006) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 42702.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Sat Oct 26 01:34:18 2024 - 00:11 ago
    State  : Sleeping, pid: 42702
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (2.7 GB VSZ)
    Started: Sat Oct 26 01:34:18 2024 - 00:13 ago
    State  : Sleeping, pid: 42702
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (2.7 GB VSZ)
    Started: Sat Oct 26 01:34:18 2024 - 00:15 ago
    State  : Sleeping, pid: 42702
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-26 01:34:38 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-26 01:34:40 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_Z2NQxl3jJ/ea_profile.json
* 2024-10-26 01:34:44 (390) [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/_Z2NQxl3jJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-26 01:34:44 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-28 01:33:25 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-28 01:33:25 (9031) [INFO] Script is up to date.
* 2024-10-28 01:33:26 (230) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-28 01:33:26 (2274) [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-10-28 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-28 01:33:27 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-28 01:33:27 (7668) [INFO] 
* 2024-10-28 01:33:31 (675) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-28 01:33:31 (682) [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.

* 2024-10-28 01:33:31 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-28 01:33:31 (7668) [INFO] 
* 2024-10-28 01:33:44 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-28 01:33:44 (2136) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-28 01:33:44 (2136) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-28 01:33:44 (2112) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-28 01:33:44 (2112) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-28 01:33:44 (2136) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-28 01:33:44 (2136) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-28 01:33:44 (2112) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-28 01:33:44 (2136) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-28 01:33:49 (1995) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-28 01:33:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-28 01:33:49 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-28 01:33:49 (7668) [INFO] 
* 2024-10-28 01:33:49 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-28 01:33:50 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-28 01:33:50 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-28 01:33:50 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-28 01:33:50 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-28 01:33:50 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-28 01:33:50 (7681) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-28 01:33:50 (7681) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-28 01:33:50 (7681) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-28 01:33:50 (7681) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-28 01:33:50 (7681) [INFO]               : yarn
* 2024-10-28 01:33:50 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-28 01:33:50 (7681) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-28 01:33:50 (7698) [INFO] 
* 2024-10-28 01:33:56 (2005) [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-10-28 01:33:56 (2006) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-28 01:33:56 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-28 01:33:58 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BIbMh2IQ5O/ea_profile.json
* 2024-10-28 01:34:02 (390) [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/BIbMh2IQ5O/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-28 01:34:02 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-29 01:33:50 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-29 01:33:50 (9014) [INFO] Newer version of script found. Downloading.
* 2024-10-29 01:33:50 (9023) [INFO] Script update to version 56 successful.
* 2024-10-29 01:33:52 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-29 01:33:52 (5878) [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-10-29 01:33:52 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-29 01:33:52 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-29 01:33:52 (7662) [INFO] 
* 2024-10-29 01:33:57 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-29 01:33:57 (3715) [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.

* 2024-10-29 01:33:57 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-29 01:33:57 (7662) [INFO] 
* 2024-10-29 01:34:15 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-29 01:34:15 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-29 01:34:15 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-29 01:34:15 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-29 01:34:15 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-29 01:34:15 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-29 01:34:15 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-29 01:34:15 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-29 01:34:15 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-29 01:34:19 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-29 01:34:19 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-29 01:34:19 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-29 01:34:19 (7662) [INFO] 
* 2024-10-29 01:34:19 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-29 01:34:19 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-29 01:34:19 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-29 01:34:19 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-29 01:34:19 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-29 01:34:19 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-29 01:34:19 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-29 01:34:19 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-29 01:34:19 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-29 01:34:19 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-29 01:34:19 (7675) [INFO]               : yarn
* 2024-10-29 01:34:20 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-29 01:34:20 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-29 01:34:20 (7692) [INFO] 
* 2024-10-29 01:34:27 (5466) [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-10-29 01:34:27 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-29 01:34:27 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-29 01:34:28 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MutvpW2h1E/ea_profile.json
* 2024-10-29 01:34:33 (488) [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/MutvpW2h1E/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-29 01:34:33 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-30 01:33:36 (8998) [INFO] Self-update of script version 56 requested.
* 2024-10-30 01:33:36 (9020) [INFO] Script is up to date.
* 2024-10-30 01:33:37 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-30 01:33:37 (5878) [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-10-30 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-30 01:33:38 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-30 01:33:38 (7662) [INFO] 
* 2024-10-30 01:33:42 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-30 01:33:42 (3715) [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.

* 2024-10-30 01:33:42 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-30 01:33:42 (7662) [INFO] 
* 2024-10-30 01:34:09 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-30 01:34:09 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-30 01:34:09 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-30 01:34:09 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-30 01:34:09 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-30 01:34:09 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-30 01:34:09 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-30 01:34:09 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-30 01:34:09 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-30 01:34:17 (5456) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 582378.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Wed Oct 30 01:33:56 2024 - 00:13 ago
    State  : Sleeping, pid: 582378
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (332 MB VSZ)
    Started: Wed Oct 30 01:33:56 2024 - 00:15 ago
    State  : Sleeping, pid: 582378
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-30 01:34:17 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-30 01:34:17 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-30 01:34:17 (7662) [INFO] 
* 2024-10-30 01:34:17 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-30 01:34:17 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-30 01:34:17 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-30 01:34:17 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-30 01:34:17 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-30 01:34:17 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-30 01:34:17 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-30 01:34:17 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-30 01:34:17 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-30 01:34:17 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-30 01:34:17 (7675) [INFO]               : yarn
* 2024-10-30 01:34:17 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-30 01:34:17 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-30 01:34:17 (7692) [INFO] 
* 2024-10-30 01:34:30 (5466) [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-10-30 01:34:30 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-30 01:34:30 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-30 01:34:31 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kChJlGsO8_/ea_profile.json
* 2024-10-30 01:34:36 (488) [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/kChJlGsO8_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-30 01:34:36 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-31 01:33:26 (8998) [INFO] Self-update of script version 56 requested.
* 2024-10-31 01:33:26 (9020) [INFO] Script is up to date.
* 2024-10-31 01:33:27 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-10-31 01:33:27 (5878) [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-10-31 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-10-31 01:33:27 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-31 01:33:27 (7662) [INFO] 
* 2024-10-31 01:33:32 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-10-31 01:33:32 (3715) [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.

* 2024-10-31 01:33:32 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-31 01:33:32 (7662) [INFO] 
* 2024-10-31 01:33:50 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-10-31 01:33:50 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-10-31 01:33:50 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-10-31 01:33:50 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-31 01:33:50 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-10-31 01:33:50 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-10-31 01:33:50 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-10-31 01:33:50 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-10-31 01:33:50 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-10-31 01:33:54 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-31 01:33:54 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-31 01:33:54 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-31 01:33:54 (7662) [INFO] 
* 2024-10-31 01:33:55 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-31 01:33:55 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-10-31 01:33:55 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-31 01:33:55 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-31 01:33:55 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-10-31 01:33:55 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-31 01:33:55 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-10-31 01:33:55 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-10-31 01:33:55 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-10-31 01:33:55 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-31 01:33:55 (7675) [INFO]               : yarn
* 2024-10-31 01:33:55 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-31 01:33:55 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-10-31 01:33:55 (7692) [INFO] 
* 2024-10-31 01:34:00 (5466) [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-10-31 01:34:00 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-10-31 01:34:00 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-31 01:34:02 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JnMcrHbrWZ/ea_profile.json
* 2024-10-31 01:34:07 (488) [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/JnMcrHbrWZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-31 01:34:07 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-01 01:34:19 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-01 01:34:19 (9020) [INFO] Script is up to date.
* 2024-11-01 01:34:20 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-01 01:34:20 (5878) [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-11-01 01:34:20 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-01 01:34:20 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-01 01:34:20 (7662) [INFO] 
* 2024-11-01 01:34:24 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-01 01:34:24 (3715) [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.

* 2024-11-01 01:34:24 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-01 01:34:24 (7662) [INFO] 
* 2024-11-01 01:34:44 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-01 01:34:44 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-01 01:34:44 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-01 01:34:44 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-01 01:34:44 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-01 01:34:44 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-01 01:34:44 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-01 01:34:44 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-01 01:34:44 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-01 01:34:49 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-01 01:34:49 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-01 01:34:49 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-01 01:34:49 (7662) [INFO] 
* 2024-11-01 01:34:50 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-01 01:34:50 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-01 01:34:50 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-01 01:34:50 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-01 01:34:50 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-01 01:34:50 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-01 01:34:50 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-01 01:34:50 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-01 01:34:50 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-01 01:34:50 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-01 01:34:50 (7675) [INFO]               : yarn
* 2024-11-01 01:34:50 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-01 01:34:50 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-01 01:34:50 (7692) [INFO] 
* 2024-11-01 01:34:56 (5466) [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-11-01 01:34:56 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-01 01:34:56 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-01 01:34:58 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sAEdUXGkDd/ea_profile.json
* 2024-11-01 01:35:03 (488) [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/sAEdUXGkDd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-01 01:35:03 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-02 01:34:11 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-02 01:34:12 (9020) [INFO] Script is up to date.
* 2024-11-02 01:34:13 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-02 01:34:13 (5878) [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-11-02 01:34:13 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-02 01:34:13 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-02 01:34:13 (7662) [INFO] 
* 2024-11-02 01:34:17 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-02 01:34:17 (3715) [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.

* 2024-11-02 01:34:17 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-02 01:34:17 (7662) [INFO] 
* 2024-11-02 01:34:26 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-02 01:34:26 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-02 01:34:26 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-02 01:34:26 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-02 01:34:26 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-02 01:34:26 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-02 01:34:26 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-02 01:34:26 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-02 01:34:26 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-02 01:34:30 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-02 01:34:30 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-02 01:34:30 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-02 01:34:30 (7662) [INFO] 
* 2024-11-02 01:34:31 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-02 01:34:31 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-02 01:34:31 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-02 01:34:31 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-02 01:34:31 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-02 01:34:31 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-02 01:34:31 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-02 01:34:31 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-02 01:34:31 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-02 01:34:31 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-02 01:34:31 (7675) [INFO]               : yarn
* 2024-11-02 01:34:31 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-02 01:34:31 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-02 01:34:31 (7692) [INFO] 
* 2024-11-02 01:34:36 (5466) [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-11-02 01:34:36 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-02 01:34:36 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-02 01:34:38 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DxdcOVHYsJ/ea_profile.json
* 2024-11-02 01:34:40 (488) [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/DxdcOVHYsJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-02 01:34:40 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-03 01:34:08 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-03 01:34:08 (9020) [INFO] Script is up to date.
* 2024-11-03 01:34:09 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-03 01:34:09 (5878) [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-11-03 01:34:09 (264) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2024-11-03 01:34:09 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-03 01:34:09 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-03 01:34:09 (7662) [INFO] 
* 2024-11-03 01:34:14 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-03 01:34:14 (3715) [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.

* 2024-11-03 01:34:14 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-03 01:34:14 (7662) [INFO] 
* 2024-11-03 01:34:28 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-03 01:34:28 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-03 01:34:28 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-03 01:34:28 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-03 01:34:28 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-03 01:34:28 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-03 01:34:28 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-03 01:34:28 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-03 01:34:28 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-03 01:34:33 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-03 01:34:33 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-03 01:34:33 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-03 01:34:33 (7662) [INFO] 
* 2024-11-03 01:34:33 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-03 01:34:33 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-03 01:34:33 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-03 01:34:33 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-03 01:34:33 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-03 01:34:33 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-03 01:34:33 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-03 01:34:33 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-03 01:34:33 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-03 01:34:33 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-03 01:34:33 (7675) [INFO]               : yarn
* 2024-11-03 01:34:33 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-03 01:34:33 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-03 01:34:33 (7692) [INFO] 
* 2024-11-03 01:34:40 (5466) [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-11-03 01:34:40 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-03 01:34:40 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-03 01:34:42 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GGs5IS1ncB/ea_profile.json
* 2024-11-03 01:34:46 (488) [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/GGs5IS1ncB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-03 01:34:46 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-04 01:33:36 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-04 01:33:36 (9020) [INFO] Script is up to date.
* 2024-11-04 01:33:37 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-04 01:33:37 (5878) [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-11-04 01:33:37 (264) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-04 01:33:37 (264) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2024-11-04 01:33:37 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-04 01:33:37 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-04 01:33:37 (7662) [INFO] 
* 2024-11-04 01:33:41 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-04 01:33:41 (3715) [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.

* 2024-11-04 01:33:41 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-04 01:33:41 (7662) [INFO] 
* 2024-11-04 01:34:03 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-04 01:34:03 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-04 01:34:03 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-04 01:34:03 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-04 01:34:03 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-04 01:34:03 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-04 01:34:03 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-04 01:34:03 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-04 01:34:03 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-04 01:34:09 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-04 01:34:09 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-04 01:34:09 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-04 01:34:09 (7662) [INFO] 
* 2024-11-04 01:34:09 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-04 01:34:09 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-04 01:34:09 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-04 01:34:09 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-04 01:34:09 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-04 01:34:09 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-04 01:34:09 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-04 01:34:09 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-04 01:34:09 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-04 01:34:09 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-04 01:34:09 (7675) [INFO]               : yarn
* 2024-11-04 01:34:09 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-04 01:34:09 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-04 01:34:09 (7692) [INFO] 
* 2024-11-04 01:34:17 (5466) [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-11-04 01:34:17 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-04 01:34:17 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-04 01:34:18 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5RDPJ2det8/ea_profile.json
* 2024-11-04 01:34:23 (488) [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/5RDPJ2det8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-04 01:34:23 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-05 01:33:37 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-05 01:33:37 (9020) [INFO] Script is up to date.
* 2024-11-05 01:33:38 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-05 01:33:38 (5878) [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-11-05 01:33:38 (264) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-05 01:33:38 (264) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2024-11-05 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-05 01:33:38 (264) [WARN] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.47) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.48.

* 2024-11-05 01:33:38 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-05 01:33:38 (7662) [INFO] 
* 2024-11-05 01:33:42 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-05 01:33:42 (3715) [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.

* 2024-11-05 01:33:42 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-05 01:33:42 (7662) [INFO] 
* 2024-11-05 01:33:58 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-05 01:33:58 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-05 01:33:58 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-05 01:33:58 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-05 01:33:58 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-05 01:33:58 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-05 01:33:58 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-05 01:33:58 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-05 01:33:58 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-05 01:34:01 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-05 01:34:01 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-05 01:34:01 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-05 01:34:01 (7662) [INFO] 
* 2024-11-05 01:34:02 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-05 01:34:02 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-05 01:34:02 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-05 01:34:02 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-05 01:34:02 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-05 01:34:02 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-05 01:34:02 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-05 01:34:02 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-05 01:34:02 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-05 01:34:02 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-05 01:34:02 (7675) [INFO]               : yarn
* 2024-11-05 01:34:02 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-05 01:34:02 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-05 01:34:02 (7692) [INFO] 
* 2024-11-05 01:34:08 (5466) [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-11-05 01:34:08 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-05 01:34:08 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-05 01:34:09 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7AluJKOsjT/ea_profile.json
* 2024-11-05 01:34:14 (488) [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/7AluJKOsjT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-05 01:34:14 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-06 01:34:31 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-06 01:34:31 (9020) [INFO] Script is up to date.
* 2024-11-06 01:34:32 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-06 01:34:32 (5878) [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-11-06 01:34:32 (264) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-06 01:34:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-06 01:34:32 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-06 01:34:32 (7662) [INFO] 
* 2024-11-06 01:34:36 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-06 01:34:36 (3715) [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.

* 2024-11-06 01:34:36 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-06 01:34:36 (7662) [INFO] 
* 2024-11-06 01:34:49 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-06 01:34:49 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-06 01:34:49 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-06 01:34:49 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-06 01:34:49 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-06 01:34:49 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-06 01:34:49 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-06 01:34:49 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-06 01:34:49 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-06 01:34:53 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-06 01:34:53 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-06 01:34:53 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-06 01:34:53 (7662) [INFO] 
* 2024-11-06 01:34:53 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-06 01:34:53 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-06 01:34:53 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-06 01:34:53 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-06 01:34:53 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-06 01:34:53 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-06 01:34:53 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-06 01:34:53 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-06 01:34:53 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-06 01:34:53 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-06 01:34:53 (7675) [INFO]               : yarn
* 2024-11-06 01:34:53 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-06 01:34:53 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-06 01:34:53 (7692) [INFO] 
* 2024-11-06 01:34:58 (5466) [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-11-06 01:34:58 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-06 01:34:58 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-06 01:34:59 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4KavxymqRL/ea_profile.json
* 2024-11-06 01:35:03 (488) [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/4KavxymqRL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-06 01:35:03 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-07 01:33:29 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-07 01:33:29 (9020) [INFO] Script is up to date.
* 2024-11-07 01:33:31 (264) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-07 01:33:31 (5878) [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-11-07 01:33:31 (264) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-07 01:33:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-07 01:33:31 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-07 01:33:31 (7662) [INFO] 
* 2024-11-07 01:33:37 (3708) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-07 01:33:37 (3715) [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.

* 2024-11-07 01:33:37 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-07 01:33:37 (7662) [INFO] 
* 2024-11-07 01:34:07 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-07 01:34:07 (5597) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-07 01:34:07 (5597) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-07 01:34:07 (5573) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-07 01:34:07 (5573) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-07 01:34:07 (5597) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-07 01:34:07 (5597) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-07 01:34:07 (5573) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-07 01:34:07 (5597) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-07 01:34:20 (5456) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-07 01:34:20 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-07 01:34:20 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-07 01:34:20 (7662) [INFO] 
* 2024-11-07 01:34:20 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-07 01:34:20 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-07 01:34:20 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-07 01:34:20 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-07 01:34:20 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-07 01:34:20 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-07 01:34:20 (7675) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-07 01:34:20 (7675) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-07 01:34:20 (7675) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-07 01:34:20 (7675) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-07 01:34:20 (7675) [INFO]               : yarn
* 2024-11-07 01:34:20 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-07 01:34:20 (7675) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-07 01:34:20 (7692) [INFO] 
* 2024-11-07 01:34:39 (5466) [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-11-07 01:34:39 (5467) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-07 01:34:39 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-07 01:34:41 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dO6otYOg3l/ea_profile.json
* 2024-11-07 01:34:47 (488) [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/dO6otYOg3l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-07 01:34:47 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-08 01:33:36 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-08 01:33:36 (9003) [INFO] Newer version of script found. Downloading.
* 2024-11-08 01:33:37 (9012) [INFO] Script update to version 57 successful.
* 2024-11-08 01:33:38 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-08 01:33:38 (5931) [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-11-08 01:33:38 (249) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-08 01:33:38 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-08 01:33:38 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-08 01:33:38 (8441) [INFO] 
* 2024-11-08 01:33:44 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-08 01:33:44 (3717) [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.

* 2024-11-08 01:33:44 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-08 01:33:44 (8441) [INFO] 
* 2024-11-08 01:34:01 (8454) [INFO] alpharide_account.wp_alp_options
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] alpharide_account.wp_alp_posts
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] dcfinanc_wp186.wpem_actionscheduler_claims
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 3 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] dcfinanc_wp186.wpem_wc_admin_note_actions
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-08 01:34:01 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-08 01:34:01 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-08 01:34:01 (8454) [INFO] error    : Corrupt
* 2024-11-08 01:34:01 (8454) [INFO] motopart_oc2.oc_customer
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 5 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-08 01:34:01 (8454) [INFO] error    : Corrupt
* 2024-11-08 01:34:01 (8454) [INFO] motopart_oc2.oc_customer_online
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 7 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] motopart_oc2.oc_product
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 7 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] motopart_production.payment_status
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-08 01:34:01 (8454) [INFO] motopart_production.users
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-08 01:34:01 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-08 01:34:01 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 01:34:01 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-08 01:34:01 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 01:34:01 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-08 01:34:01 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 01:34:01 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-08 01:34:01 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 01:34:01 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-08 01:34:01 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 01:34:01 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-08 01:34:01 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 01:34:01 (8454) [INFO] ncfnigeria_walkfornature.wp_options
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-08 01:34:01 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-08 01:34:01 (8454) [INFO] error    : Corrupt
* 2024-11-08 01:34:01 (8454) [INFO] optisoft_blog.wp_options
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 8 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] qui10000_lhlp1.livehelp_sessions
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-08 01:34:01 (8454) [INFO] error    : Corrupt
* 2024-11-08 01:34:01 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-08 01:34:01 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-08 01:34:01 (8454) [INFO] error    : Corrupt
* 2024-11-08 01:34:01 (8454) [INFO] qui10000_ve.product
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 8 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8454) [INFO] qui10000_ve.review
* 2024-11-08 01:34:01 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-08 01:34:01 (8471) [INFO] 
* 2024-11-08 01:34:01 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
alpharide_account.wp_alp_options
warning  : 2 clients are using or haven't closed the table properly
alpharide_account.wp_alp_posts
warning  : 1 client is using or hasn't closed the table properly
dcfinanc_wp186.wpem_actionscheduler_claims
warning  : 3 clients are using or haven't closed the table properly
dcfinanc_wp186.wpem_wc_admin_note_actions
warning  : 1 client is using or hasn't closed the table properly
motopart_oc2.oc_address
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer
warning  : 5 clients are using or haven't closed the table properly
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_oc2.oc_customer_online
warning  : 7 clients are using or haven't closed the table properly
motopart_oc2.oc_product
warning  : 7 clients are using or haven't closed the table properly
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_walkfornature.wp_options
warning  : 1 client is using or hasn't closed the table properly
optisoft_blog.wp_comments
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
optisoft_blog.wp_options
warning  : 8 clients are using or haven't closed the table properly
qui10000_lhlp1.livehelp_sessions
warning  : 2 clients are using or haven't closed the table properly
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
qui10000_ve.product
warning  : 8 clients are using or haven't closed the table properly
qui10000_ve.review
warning  : 2 clients are using or haven't closed the table properly
You should repair any corrupted databases before elevating the system.

* 2024-11-08 01:34:01 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-08 01:34:01 (8441) [INFO] 
* 2024-11-08 01:34:10 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-08 01:34:10 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-08 01:34:10 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-08 01:34:10 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-08 01:34:10 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-08 01:34:10 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-08 01:34:10 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-08 01:34:10 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-08 01:34:10 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-08 01:34:10 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-08 01:34:10 (8441) [INFO] 
* 2024-11-08 01:34:10 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 01:34:10 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-08 01:34:12 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-08 01:34:12 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-08 01:34:12 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-08 01:34:12 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-08 01:34:12 (8454) [INFO]  * remi-php72: mirror.netweaver.uk
* 2024-11-08 01:34:12 (8454) [INFO]  * remi-php73: mirror.netweaver.uk
* 2024-11-08 01:34:12 (8454) [INFO]  * remi-safe: mirror.netweaver.uk
* 2024-11-08 01:34:14 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-08 01:34:15 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-08 01:34:15 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-08 01:34:15 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-08 01:34:15 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-08 01:34:15 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-08 01:34:15 (8454) [INFO] Trying other mirror.
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-08 01:34:15 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 01:34:15 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 01:34:15 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-08 01:34:15 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-08 01:34:15 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-08 01:34:15 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 01:34:15 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-08 01:34:15 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-08 01:34:15 (8454) [INFO]         or
* 2024-11-08 01:34:15 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 01:34:15 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 01:34:15 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 01:34:15 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 01:34:15 (8454) [INFO]         compromise:
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-08 01:34:15 (8454) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-08 01:34:15 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-08 01:34:15 (8471) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-08 01:34:15 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-08 01:34:15 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-08 01:34:15 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-08 01:34:15 (8441) [INFO] 
* 2024-11-08 01:34:15 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 01:34:15 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-08 01:34:15 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-08 01:34:15 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-08 01:34:15 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-08 01:34:15 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-08 01:34:15 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-08 01:34:15 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-08 01:34:15 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-08 01:34:15 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-08 01:34:15 (8454) [INFO]               : yarn
* 2024-11-08 01:34:15 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-08 01:34:15 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-08 01:34:15 (8471) [INFO] 
* 2024-11-08 01:34:15 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-08 01:34:15 (8441) [INFO] 
* 2024-11-08 01:34:16 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 01:34:16 (8454) [INFO] Determining fastest mirrors
* 2024-11-08 01:34:22 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-08 01:34:22 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-08 01:34:22 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-08 01:34:22 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-08 01:34:22 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-08 01:34:22 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-08 01:34:22 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-08 01:34:25 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-08 01:34:25 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-08 01:34:25 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-08 01:34:25 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-08 01:34:25 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-08 01:34:25 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-08 01:34:25 (8454) [INFO] Trying other mirror.
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-08 01:34:25 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 01:34:25 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 01:34:25 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-08 01:34:25 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-08 01:34:25 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-08 01:34:25 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 01:34:25 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-08 01:34:25 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-08 01:34:25 (8454) [INFO]         or
* 2024-11-08 01:34:25 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 01:34:25 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 01:34:25 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 01:34:25 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 01:34:25 (8454) [INFO]         compromise:
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-08 01:34:25 (8454) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-08 01:34:25 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-08 01:34:25 (8471) [INFO] 
* 2024-11-08 01:34:25 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-08 01:34:25 (5517) [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-11-08 01:34:25 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-08 01:34:26 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-08 01:34:27 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xffMBVTZbc/ea_profile.json
* 2024-11-08 01:34:32 (475) [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/xffMBVTZbc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-08 01:34:32 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-09 01:34:13 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-09 01:34:13 (9513) [INFO] Script is up to date.
* 2024-11-09 01:34:14 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-09 01:34:14 (5931) [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-11-09 01:34:14 (249) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-09 01:34:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-09 01:34:14 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-09 01:34:14 (8441) [INFO] 
* 2024-11-09 01:44:08 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-09 01:44:08 (3717) [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.

* 2024-11-09 01:44:08 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-09 01:44:08 (8441) [INFO] 
* 2024-11-09 01:44:26 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-09 01:44:26 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-09 01:44:26 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-09 01:44:26 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-09 01:44:26 (8454) [INFO] error    : Corrupt
* 2024-11-09 01:44:26 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-09 01:44:26 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-09 01:44:26 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-09 01:44:26 (8454) [INFO] error    : Corrupt
* 2024-11-09 01:44:26 (8454) [INFO] motopart_production.payment_status
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-09 01:44:26 (8454) [INFO] motopart_production.users
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-09 01:44:26 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-09 01:44:26 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 01:44:26 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-09 01:44:26 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 01:44:26 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-09 01:44:26 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 01:44:26 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-09 01:44:26 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 01:44:26 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-09 01:44:26 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 01:44:26 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-09 01:44:26 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 01:44:26 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-09 01:44:26 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-09 01:44:26 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-09 01:44:26 (8454) [INFO] error    : Corrupt
* 2024-11-09 01:44:26 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-09 01:44:26 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-09 01:44:26 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-09 01:44:26 (8454) [INFO] error    : Corrupt
* 2024-11-09 01:44:26 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-09 01:44:26 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-09 01:44:26 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-09 01:44:26 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-09 01:44:26 (8454) [INFO] error    : Corrupt
* 2024-11-09 01:44:26 (8471) [INFO] 
* 2024-11-09 01:44:26 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-09 01:44:26 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-09 01:44:26 (8441) [INFO] 
* 2024-11-09 01:44:31 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-09 01:44:31 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-09 01:44:31 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-09 01:44:31 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-09 01:44:31 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-09 01:44:31 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-09 01:44:31 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-09 01:44:31 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-09 01:44:31 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-09 01:44:31 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-09 01:44:31 (8441) [INFO] 
* 2024-11-09 01:44:31 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 01:44:32 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-09 01:44:34 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-09 01:44:34 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-09 01:44:34 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-09 01:44:34 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-09 01:44:34 (8454) [INFO]  * remi-php72: mirrors.upr.edu
* 2024-11-09 01:44:34 (8454) [INFO]  * remi-php73: mirrors.upr.edu
* 2024-11-09 01:44:34 (8454) [INFO]  * remi-safe: mirrors.upr.edu
* 2024-11-09 01:44:38 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-09 01:44:38 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-09 01:44:38 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-09 01:44:38 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-09 01:44:38 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-09 01:44:38 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-09 01:44:38 (8454) [INFO] Trying other mirror.
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-09 01:44:38 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 01:44:38 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 01:44:38 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-09 01:44:38 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-09 01:44:38 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-09 01:44:38 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 01:44:38 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-09 01:44:38 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-09 01:44:38 (8454) [INFO]         or
* 2024-11-09 01:44:38 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 01:44:38 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 01:44:38 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 01:44:38 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 01:44:38 (8454) [INFO]         compromise:
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-09 01:44:38 (8454) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-09 01:44:38 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-09 01:44:38 (8471) [INFO] 
* 2024-11-09 01:44:38 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-09 01:44:38 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-09 01:44:38 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-09 01:44:38 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-09 01:44:38 (8441) [INFO] 
* 2024-11-09 01:44:39 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 01:44:39 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-09 01:44:39 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-09 01:44:39 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-09 01:44:39 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-09 01:44:39 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-09 01:44:39 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-09 01:44:39 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-09 01:44:39 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-09 01:44:39 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-09 01:44:39 (8454) [INFO]               : yarn
* 2024-11-09 01:44:39 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-09 01:44:39 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-09 01:44:39 (8471) [INFO] 
* 2024-11-09 01:44:39 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-09 01:44:39 (8441) [INFO] 
* 2024-11-09 01:44:39 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 01:44:39 (8454) [INFO] Determining fastest mirrors
* 2024-11-09 01:44:46 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-09 01:44:46 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-09 01:44:46 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-09 01:44:46 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-09 01:44:46 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-09 01:44:46 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-09 01:44:46 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-09 01:44:50 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-09 01:44:50 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-09 01:44:50 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-09 01:44:50 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-09 01:44:50 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-09 01:44:50 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-09 01:44:50 (8454) [INFO] Trying other mirror.
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-09 01:44:50 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 01:44:50 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 01:44:50 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-09 01:44:50 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-09 01:44:50 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-09 01:44:50 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 01:44:50 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-09 01:44:50 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-09 01:44:50 (8454) [INFO]         or
* 2024-11-09 01:44:50 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 01:44:50 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 01:44:50 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 01:44:50 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 01:44:50 (8454) [INFO]         compromise:
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-09 01:44:50 (8454) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-09 01:44:50 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-09 01:44:50 (8471) [INFO] 
* 2024-11-09 01:44:50 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-09 01:44:50 (5517) [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-11-09 01:44:50 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-09 01:44:51 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-09 01:44:52 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xoGDWagnrm/ea_profile.json
* 2024-11-09 01:44:58 (475) [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/xoGDWagnrm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-09 01:44:58 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-10 01:33:59 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-10 01:33:59 (9513) [INFO] Script is up to date.
* 2024-11-10 01:34:00 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-10 01:34:00 (5931) [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-11-10 01:34:00 (249) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-10 01:34:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-10 01:34:00 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-10 01:34:00 (8441) [INFO] 
* 2024-11-10 01:39:09 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-10 01:39:09 (3717) [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.

* 2024-11-10 01:39:09 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-10 01:39:09 (8441) [INFO] 
* 2024-11-10 01:39:27 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-10 01:39:27 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-10 01:39:27 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-10 01:39:27 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-10 01:39:27 (8454) [INFO] error    : Corrupt
* 2024-11-10 01:39:27 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-10 01:39:27 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-10 01:39:27 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-10 01:39:27 (8454) [INFO] error    : Corrupt
* 2024-11-10 01:39:27 (8454) [INFO] motopart_production.payment_status
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-10 01:39:27 (8454) [INFO] motopart_production.users
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-10 01:39:27 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-10 01:39:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 01:39:27 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-10 01:39:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 01:39:27 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-10 01:39:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 01:39:27 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-10 01:39:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 01:39:27 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-10 01:39:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 01:39:27 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-10 01:39:27 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 01:39:27 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-10 01:39:27 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-10 01:39:27 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-10 01:39:27 (8454) [INFO] error    : Corrupt
* 2024-11-10 01:39:27 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-10 01:39:27 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-10 01:39:27 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-10 01:39:27 (8454) [INFO] error    : Corrupt
* 2024-11-10 01:39:27 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-10 01:39:27 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-10 01:39:27 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-10 01:39:27 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-10 01:39:27 (8454) [INFO] error    : Corrupt
* 2024-11-10 01:39:27 (8471) [INFO] 
* 2024-11-10 01:39:27 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-10 01:39:27 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-10 01:39:27 (8441) [INFO] 
* 2024-11-10 01:39:30 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-10 01:39:30 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-10 01:39:30 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-10 01:39:30 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-10 01:39:30 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-10 01:39:30 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-10 01:39:30 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-10 01:39:30 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-10 01:39:30 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-10 01:39:30 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-10 01:39:30 (8441) [INFO] 
* 2024-11-10 01:39:31 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 01:39:31 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-10 01:39:32 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-10 01:39:32 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-10 01:39:32 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-10 01:39:32 (8454) [INFO]  * epel: dl.fedoraproject.org
* 2024-11-10 01:39:32 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-10 01:39:32 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-10 01:39:32 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-10 01:39:34 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-10 01:39:34 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-10 01:39:34 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-10 01:39:34 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-10 01:39:34 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-10 01:39:34 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-10 01:39:34 (8454) [INFO] Trying other mirror.
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-10 01:39:34 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 01:39:34 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 01:39:34 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-10 01:39:34 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-10 01:39:34 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-10 01:39:34 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 01:39:34 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-10 01:39:34 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-10 01:39:34 (8454) [INFO]         or
* 2024-11-10 01:39:34 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 01:39:34 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 01:39:34 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 01:39:34 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 01:39:34 (8454) [INFO]         compromise:
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-10 01:39:34 (8454) [INFO] 
* 2024-11-10 01:39:34 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-10 01:39:34 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-10 01:39:35 (8471) [INFO] 
* 2024-11-10 01:39:35 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-10 01:39:35 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-10 01:39:35 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-10 01:39:35 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-10 01:39:35 (8441) [INFO] 
* 2024-11-10 01:39:35 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 01:39:35 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-10 01:39:35 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-10 01:39:35 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-10 01:39:35 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-10 01:39:35 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-10 01:39:35 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-10 01:39:35 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-10 01:39:35 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-10 01:39:35 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-10 01:39:35 (8454) [INFO]               : yarn
* 2024-11-10 01:39:35 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-10 01:39:35 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-10 01:39:35 (8471) [INFO] 
* 2024-11-10 01:39:35 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-10 01:39:35 (8441) [INFO] 
* 2024-11-10 01:39:35 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 01:39:35 (8454) [INFO] Determining fastest mirrors
* 2024-11-10 01:39:37 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-10 01:39:37 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-10 01:39:37 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-10 01:39:37 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-10 01:39:37 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-10 01:39:37 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-10 01:39:37 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-10 01:39:40 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-10 01:39:40 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-10 01:39:40 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-10 01:39:40 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-10 01:39:40 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-10 01:39:40 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-10 01:39:40 (8454) [INFO] Trying other mirror.
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-10 01:39:40 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 01:39:40 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 01:39:40 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-10 01:39:40 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-10 01:39:40 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-10 01:39:40 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 01:39:40 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-10 01:39:40 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-10 01:39:40 (8454) [INFO]         or
* 2024-11-10 01:39:40 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 01:39:40 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 01:39:40 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 01:39:40 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 01:39:40 (8454) [INFO]         compromise:
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-10 01:39:40 (8454) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-10 01:39:40 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-10 01:39:40 (8471) [INFO] 
* 2024-11-10 01:39:40 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-10 01:39:40 (5517) [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-11-10 01:39:40 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-10 01:39:40 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-10 01:39:41 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b9G4WdIn_i/ea_profile.json
* 2024-11-10 01:39:46 (475) [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/b9G4WdIn_i/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-10 01:39:46 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-11 01:33:25 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-11 01:33:25 (9513) [INFO] Script is up to date.
* 2024-11-11 01:33:26 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-11 01:33:26 (5931) [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-11-11 01:33:26 (249) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-11-11 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-11 01:33:26 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-11 01:33:26 (8441) [INFO] 
* 2024-11-11 01:33:31 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-11 01:33:31 (3717) [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.

* 2024-11-11 01:33:31 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-11 01:33:31 (8441) [INFO] 
* 2024-11-11 01:33:46 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-11 01:33:46 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-11 01:33:46 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-11 01:33:46 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-11 01:33:46 (8454) [INFO] error    : Corrupt
* 2024-11-11 01:33:46 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-11 01:33:46 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-11 01:33:46 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-11 01:33:46 (8454) [INFO] error    : Corrupt
* 2024-11-11 01:33:46 (8454) [INFO] motopart_production.payment_status
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-11 01:33:46 (8454) [INFO] motopart_production.users
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-11 01:33:46 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-11 01:33:46 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 01:33:46 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-11 01:33:46 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 01:33:46 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-11 01:33:46 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 01:33:46 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-11 01:33:46 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 01:33:46 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-11 01:33:46 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 01:33:46 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-11 01:33:46 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 01:33:46 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-11 01:33:46 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-11 01:33:46 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-11 01:33:46 (8454) [INFO] error    : Corrupt
* 2024-11-11 01:33:46 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-11 01:33:46 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-11 01:33:46 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-11 01:33:46 (8454) [INFO] error    : Corrupt
* 2024-11-11 01:33:46 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-11 01:33:46 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-11 01:33:46 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-11 01:33:46 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-11 01:33:46 (8454) [INFO] error    : Corrupt
* 2024-11-11 01:33:46 (8471) [INFO] 
* 2024-11-11 01:33:46 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-11 01:33:46 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-11 01:33:46 (8441) [INFO] 
* 2024-11-11 01:33:49 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-11 01:33:49 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-11 01:33:49 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-11 01:33:49 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-11 01:33:49 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-11 01:33:49 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-11 01:33:49 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-11 01:33:49 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-11 01:33:49 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-11 01:33:49 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-11 01:33:49 (8441) [INFO] 
* 2024-11-11 01:33:49 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 01:33:49 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-11 01:33:51 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-11 01:33:51 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-11 01:33:51 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-11 01:33:51 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-11 01:33:51 (8454) [INFO]  * remi-php72: remi.mirror.ate.info
* 2024-11-11 01:33:51 (8454) [INFO]  * remi-php73: remi.mirror.ate.info
* 2024-11-11 01:33:51 (8454) [INFO]  * remi-safe: remi.mirror.ate.info
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]  One of the configured repositories failed (Unknown),
* 2024-11-11 01:33:51 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 01:33:51 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 01:33:51 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-11 01:33:51 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-11 01:33:51 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-11 01:33:51 (8454) [INFO]             yum --disablerepo=<repoid> ...
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 01:33:51 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-11 01:33:51 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]             yum-config-manager --disable <repoid>
* 2024-11-11 01:33:51 (8454) [INFO]         or
* 2024-11-11 01:33:51 (8454) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 01:33:51 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 01:33:51 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 01:33:51 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 01:33:51 (8454) [INFO]         compromise:
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-11 01:33:51 (8454) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2024-11-11 01:33:51 (8454) [INFO]     * free   0 
* 2024-11-11 01:33:51 (8454) [INFO]     * needed 100 k
* 2024-11-11 01:33:51 (8471) [INFO] 
* 2024-11-11 01:33:51 (5507) [WARN] Initial run of "yum makecache" failed: 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-11-11 01:33:51 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-11 01:33:51 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-11 01:33:51 (8441) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 01:33:51 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-11 01:33:51 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-11 01:33:51 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-11 01:33:51 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-11 01:33:51 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-11 01:33:51 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-11 01:33:51 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-11 01:33:51 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-11 01:33:51 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-11 01:33:51 (8454) [INFO]               : yarn
* 2024-11-11 01:33:51 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-11 01:33:51 (8454) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-11-11 01:33:51 (8471) [INFO] 
* 2024-11-11 01:33:51 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-11 01:33:51 (8441) [INFO] 
* 2024-11-11 01:33:51 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 01:33:52 (8454) [INFO] Determining fastest mirrors
* 2024-11-11 01:33:54 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-11 01:33:54 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-11 01:33:54 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-11 01:33:54 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-11 01:33:54 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-11 01:33:54 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-11 01:33:54 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]  One of the configured repositories failed (Unknown),
* 2024-11-11 01:33:54 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 01:33:54 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 01:33:54 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-11 01:33:54 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-11 01:33:54 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-11 01:33:54 (8454) [INFO]             yum --disablerepo=<repoid> ...
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 01:33:54 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-11 01:33:54 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]             yum-config-manager --disable <repoid>
* 2024-11-11 01:33:54 (8454) [INFO]         or
* 2024-11-11 01:33:54 (8454) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 01:33:54 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 01:33:54 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 01:33:54 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 01:33:54 (8454) [INFO]         compromise:
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-11 01:33:54 (8454) [INFO] 
* 2024-11-11 01:33:54 (8454) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2024-11-11 01:33:54 (8454) [INFO]     * free   0 
* 2024-11-11 01:33:54 (8454) [INFO]     * needed 100 k
* 2024-11-11 01:33:54 (8471) [INFO] 
* 2024-11-11 01:33:54 (5517) [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-11-11 01:33:54 (5518) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-11-11 01:33:54 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-11 01:33:56 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FoE6jrnTCD/ea_profile.json
* 2024-11-11 01:33:56 (475) [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/FoE6jrnTCD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-11 01:33:56 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-12 01:33:28 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-12 01:33:28 (9513) [INFO] Script is up to date.
* 2024-11-12 01:33:29 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-12 01:33:29 (5931) [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-11-12 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-12 01:33:29 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-12 01:33:29 (8441) [INFO] 
* 2024-11-12 01:33:33 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-12 01:33:33 (3717) [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.

* 2024-11-12 01:33:33 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-12 01:33:33 (8441) [INFO] 
* 2024-11-12 01:33:50 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-12 01:33:50 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-12 01:33:50 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-12 01:33:50 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-12 01:33:50 (8454) [INFO] error    : Corrupt
* 2024-11-12 01:33:50 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-12 01:33:50 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-12 01:33:50 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-12 01:33:50 (8454) [INFO] error    : Corrupt
* 2024-11-12 01:33:50 (8454) [INFO] motopart_production.payment_status
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-12 01:33:50 (8454) [INFO] motopart_production.users
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-12 01:33:50 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-12 01:33:50 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 01:33:50 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-12 01:33:50 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 01:33:50 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-12 01:33:50 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 01:33:50 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-12 01:33:50 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 01:33:50 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-12 01:33:50 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 01:33:50 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-12 01:33:50 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 01:33:50 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-12 01:33:50 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-12 01:33:50 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-12 01:33:50 (8454) [INFO] error    : Corrupt
* 2024-11-12 01:33:50 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-12 01:33:50 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-12 01:33:50 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-12 01:33:50 (8454) [INFO] error    : Corrupt
* 2024-11-12 01:33:50 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-12 01:33:50 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-12 01:33:50 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-12 01:33:50 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-12 01:33:50 (8454) [INFO] error    : Corrupt
* 2024-11-12 01:33:50 (8471) [INFO] 
* 2024-11-12 01:33:50 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-12 01:33:50 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-12 01:33:50 (8441) [INFO] 
* 2024-11-12 01:33:56 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-12 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-12 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-12 01:33:56 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-12 01:33:56 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-12 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-12 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-12 01:33:56 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-12 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-12 01:33:56 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-12 01:33:56 (8441) [INFO] 
* 2024-11-12 01:33:57 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 01:33:57 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-12 01:33:59 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-12 01:33:59 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-12 01:33:59 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-12 01:33:59 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-12 01:33:59 (8454) [INFO]  * remi-php72: mirror.netweaver.uk
* 2024-11-12 01:33:59 (8454) [INFO]  * remi-php73: mirror.netweaver.uk
* 2024-11-12 01:33:59 (8454) [INFO]  * remi-safe: mirror.netweaver.uk
* 2024-11-12 01:34:02 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-12 01:34:02 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-12 01:34:02 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-12 01:34:02 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-12 01:34:02 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-12 01:34:02 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-12 01:34:02 (8454) [INFO] Trying other mirror.
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-12 01:34:02 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 01:34:02 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 01:34:02 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-12 01:34:02 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-12 01:34:02 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-12 01:34:02 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 01:34:02 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-12 01:34:02 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-12 01:34:02 (8454) [INFO]         or
* 2024-11-12 01:34:02 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 01:34:02 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 01:34:02 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 01:34:02 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 01:34:02 (8454) [INFO]         compromise:
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-12 01:34:02 (8454) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-12 01:34:02 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-12 01:34:02 (8471) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-12 01:34:02 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-12 01:34:02 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-12 01:34:02 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-12 01:34:02 (8441) [INFO] 
* 2024-11-12 01:34:02 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 01:34:03 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-12 01:34:03 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-12 01:34:03 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-12 01:34:03 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-12 01:34:03 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-12 01:34:03 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-12 01:34:03 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-12 01:34:03 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-12 01:34:03 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-12 01:34:03 (8454) [INFO]               : yarn
* 2024-11-12 01:34:03 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-12 01:34:03 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-12 01:34:03 (8471) [INFO] 
* 2024-11-12 01:34:03 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-12 01:34:03 (8441) [INFO] 
* 2024-11-12 01:34:03 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 01:34:03 (8454) [INFO] Determining fastest mirrors
* 2024-11-12 01:34:07 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-12 01:34:07 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-12 01:34:07 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-12 01:34:07 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-12 01:34:07 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-12 01:34:07 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-12 01:34:07 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-12 01:34:11 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-12 01:34:11 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-12 01:34:11 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-12 01:34:11 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-12 01:34:11 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-12 01:34:11 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-12 01:34:11 (8454) [INFO] Trying other mirror.
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-12 01:34:11 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 01:34:11 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 01:34:11 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-12 01:34:11 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-12 01:34:11 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-12 01:34:11 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 01:34:11 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-12 01:34:11 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-12 01:34:11 (8454) [INFO]         or
* 2024-11-12 01:34:11 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 01:34:11 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 01:34:11 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 01:34:11 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 01:34:11 (8454) [INFO]         compromise:
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-12 01:34:11 (8454) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-12 01:34:11 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-12 01:34:11 (8471) [INFO] 
* 2024-11-12 01:34:11 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-12 01:34:11 (5517) [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-11-12 01:34:11 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-12 01:34:11 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-12 01:34:12 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bsOBeqlJ72/ea_profile.json
* 2024-11-12 01:34:18 (475) [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/bsOBeqlJ72/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-12 01:34:18 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-13 01:33:26 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-13 01:33:26 (9513) [INFO] Script is up to date.
* 2024-11-13 01:33:27 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-13 01:33:27 (5931) [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-11-13 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-13 01:33:27 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-13 01:33:27 (8441) [INFO] 
* 2024-11-13 01:33:32 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-13 01:33:32 (3717) [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.

* 2024-11-13 01:33:32 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-13 01:33:32 (8441) [INFO] 
* 2024-11-13 01:33:47 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-13 01:33:47 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-13 01:33:47 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-13 01:33:47 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-13 01:33:47 (8454) [INFO] error    : Corrupt
* 2024-11-13 01:33:47 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-13 01:33:47 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-13 01:33:47 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-13 01:33:47 (8454) [INFO] error    : Corrupt
* 2024-11-13 01:33:47 (8454) [INFO] motopart_production.payment_status
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-13 01:33:47 (8454) [INFO] motopart_production.users
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-13 01:33:47 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-13 01:33:47 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 01:33:47 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-13 01:33:47 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 01:33:47 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-13 01:33:47 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 01:33:47 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-13 01:33:47 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 01:33:47 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-13 01:33:47 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 01:33:47 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-13 01:33:47 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 01:33:47 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-13 01:33:47 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-13 01:33:47 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-13 01:33:47 (8454) [INFO] error    : Corrupt
* 2024-11-13 01:33:47 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-13 01:33:47 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-13 01:33:47 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-13 01:33:47 (8454) [INFO] error    : Corrupt
* 2024-11-13 01:33:47 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-13 01:33:47 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-13 01:33:47 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-13 01:33:47 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-13 01:33:47 (8454) [INFO] error    : Corrupt
* 2024-11-13 01:33:47 (8471) [INFO] 
* 2024-11-13 01:33:47 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-13 01:33:47 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-13 01:33:47 (8441) [INFO] 
* 2024-11-13 01:33:52 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-13 01:33:52 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-13 01:33:52 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-13 01:33:52 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-13 01:33:52 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-13 01:33:52 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-13 01:33:52 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-13 01:33:52 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-13 01:33:52 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-13 01:33:52 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-13 01:33:52 (8441) [INFO] 
* 2024-11-13 01:33:53 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 01:33:53 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-13 01:33:54 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-13 01:33:54 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-13 01:33:54 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-13 01:33:54 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-13 01:33:54 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-13 01:33:54 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-13 01:33:54 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-13 01:33:57 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-13 01:33:58 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-13 01:33:58 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-13 01:33:58 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-13 01:33:58 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-13 01:33:58 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-13 01:33:58 (8454) [INFO] Trying other mirror.
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-13 01:33:58 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 01:33:58 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 01:33:58 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-13 01:33:58 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-13 01:33:58 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-13 01:33:58 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 01:33:58 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-13 01:33:58 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-13 01:33:58 (8454) [INFO]         or
* 2024-11-13 01:33:58 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 01:33:58 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 01:33:58 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 01:33:58 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 01:33:58 (8454) [INFO]         compromise:
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-13 01:33:58 (8454) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-13 01:33:58 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-13 01:33:58 (8471) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-13 01:33:58 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-13 01:33:58 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-13 01:33:58 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-13 01:33:58 (8441) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 01:33:58 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-13 01:33:58 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-13 01:33:58 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-13 01:33:58 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-13 01:33:58 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-13 01:33:58 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-13 01:33:58 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-13 01:33:58 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-13 01:33:58 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-13 01:33:58 (8454) [INFO]               : yarn
* 2024-11-13 01:33:58 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-13 01:33:58 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-13 01:33:58 (8471) [INFO] 
* 2024-11-13 01:33:58 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-13 01:33:58 (8441) [INFO] 
* 2024-11-13 01:33:58 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 01:33:58 (8454) [INFO] Determining fastest mirrors
* 2024-11-13 01:34:01 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-13 01:34:01 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-13 01:34:01 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-13 01:34:01 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-13 01:34:01 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-13 01:34:01 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-13 01:34:01 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-13 01:34:04 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-13 01:34:04 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-13 01:34:04 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-13 01:34:04 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-13 01:34:04 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-13 01:34:04 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-13 01:34:04 (8454) [INFO] Trying other mirror.
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-13 01:34:04 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 01:34:04 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 01:34:04 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-13 01:34:04 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-13 01:34:04 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-13 01:34:04 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 01:34:04 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-13 01:34:04 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-13 01:34:04 (8454) [INFO]         or
* 2024-11-13 01:34:04 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 01:34:04 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 01:34:04 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 01:34:04 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 01:34:04 (8454) [INFO]         compromise:
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-13 01:34:04 (8454) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-13 01:34:04 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-13 01:34:04 (8471) [INFO] 
* 2024-11-13 01:34:04 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-13 01:34:04 (5517) [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-11-13 01:34:04 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-13 01:34:05 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-13 01:34:06 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Kuy60CAskR/ea_profile.json
* 2024-11-13 01:34:11 (475) [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/Kuy60CAskR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-13 01:34:11 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-14 01:33:26 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-14 01:33:26 (9513) [INFO] Script is up to date.
* 2024-11-14 01:33:28 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-14 01:33:28 (5931) [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-11-14 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-14 01:33:28 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-14 01:33:28 (8441) [INFO] 
* 2024-11-14 01:33:48 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-14 01:33:48 (3717) [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.

* 2024-11-14 01:33:48 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-14 01:33:48 (8441) [INFO] 
* 2024-11-14 01:34:04 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-14 01:34:04 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-14 01:34:04 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-14 01:34:04 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-14 01:34:04 (8454) [INFO] error    : Corrupt
* 2024-11-14 01:34:04 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-14 01:34:04 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-14 01:34:04 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-14 01:34:04 (8454) [INFO] error    : Corrupt
* 2024-11-14 01:34:04 (8454) [INFO] motopart_production.payment_status
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-14 01:34:04 (8454) [INFO] motopart_production.users
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-14 01:34:04 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-14 01:34:04 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 01:34:04 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-14 01:34:04 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 01:34:04 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-14 01:34:04 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 01:34:04 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-14 01:34:04 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 01:34:04 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-14 01:34:04 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 01:34:04 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-14 01:34:04 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 01:34:04 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-14 01:34:04 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-14 01:34:04 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-14 01:34:04 (8454) [INFO] error    : Corrupt
* 2024-11-14 01:34:04 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-14 01:34:04 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-14 01:34:04 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-14 01:34:04 (8454) [INFO] error    : Corrupt
* 2024-11-14 01:34:04 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-14 01:34:04 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-14 01:34:04 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-14 01:34:04 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-14 01:34:04 (8454) [INFO] error    : Corrupt
* 2024-11-14 01:34:04 (8471) [INFO] 
* 2024-11-14 01:34:04 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-14 01:34:04 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-14 01:34:04 (8441) [INFO] 
* 2024-11-14 01:34:12 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-14 01:34:12 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-14 01:34:12 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-14 01:34:12 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-14 01:34:12 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-14 01:34:12 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-14 01:34:12 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-14 01:34:12 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-14 01:34:12 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-14 01:34:12 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-14 01:34:12 (8441) [INFO] 
* 2024-11-14 01:34:12 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 01:34:12 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-14 01:34:13 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-14 01:34:13 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-14 01:34:13 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-14 01:34:13 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-14 01:34:13 (8454) [INFO]  * remi-php72: mirror.team-cymru.com
* 2024-11-14 01:34:13 (8454) [INFO]  * remi-php73: mirror.team-cymru.com
* 2024-11-14 01:34:13 (8454) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-14 01:34:17 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-14 01:34:17 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-14 01:34:17 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-14 01:34:17 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-14 01:34:17 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-14 01:34:17 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-14 01:34:17 (8454) [INFO] Trying other mirror.
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-14 01:34:17 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 01:34:17 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 01:34:17 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-14 01:34:17 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-14 01:34:17 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-14 01:34:17 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 01:34:17 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-14 01:34:17 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-14 01:34:17 (8454) [INFO]         or
* 2024-11-14 01:34:17 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 01:34:17 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 01:34:17 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 01:34:17 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 01:34:17 (8454) [INFO]         compromise:
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-14 01:34:17 (8454) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-14 01:34:17 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-14 01:34:17 (8471) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-14 01:34:17 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-14 01:34:17 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-14 01:34:17 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-14 01:34:17 (8441) [INFO] 
* 2024-11-14 01:34:17 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 01:34:18 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-14 01:34:18 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-14 01:34:18 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-14 01:34:18 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-14 01:34:18 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-14 01:34:18 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-14 01:34:18 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-14 01:34:18 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-14 01:34:18 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-14 01:34:18 (8454) [INFO]               : yarn
* 2024-11-14 01:34:18 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-14 01:34:18 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-14 01:34:18 (8471) [INFO] 
* 2024-11-14 01:34:18 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-14 01:34:18 (8441) [INFO] 
* 2024-11-14 01:34:18 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 01:34:18 (8454) [INFO] Determining fastest mirrors
* 2024-11-14 01:34:21 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-14 01:34:21 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-14 01:34:21 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-14 01:34:21 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-14 01:34:21 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-14 01:34:21 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-14 01:34:21 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-14 01:34:25 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-14 01:34:25 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-14 01:34:25 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-14 01:34:25 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-14 01:34:25 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-14 01:34:25 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-14 01:34:25 (8454) [INFO] Trying other mirror.
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-14 01:34:25 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 01:34:25 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 01:34:25 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-14 01:34:25 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-14 01:34:25 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-14 01:34:25 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 01:34:25 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-14 01:34:25 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-14 01:34:25 (8454) [INFO]         or
* 2024-11-14 01:34:25 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 01:34:25 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 01:34:25 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 01:34:25 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 01:34:25 (8454) [INFO]         compromise:
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-14 01:34:25 (8454) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-14 01:34:25 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-14 01:34:25 (8471) [INFO] 
* 2024-11-14 01:34:25 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-14 01:34:25 (5517) [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-11-14 01:34:25 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-14 01:34:25 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-14 01:34:26 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6u2KpV0uuh/ea_profile.json
* 2024-11-14 01:34:30 (475) [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/6u2KpV0uuh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-14 01:34:30 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-15 01:33:32 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-15 01:33:32 (9513) [INFO] Script is up to date.
* 2024-11-15 01:33:33 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-15 01:33:33 (5931) [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-11-15 01:33:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-15 01:33:33 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-15 01:33:33 (8441) [INFO] 
* 2024-11-15 01:33:37 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-15 01:33:37 (3717) [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.

* 2024-11-15 01:33:37 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-15 01:33:37 (8441) [INFO] 
* 2024-11-15 01:34:00 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-15 01:34:00 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-15 01:34:00 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-15 01:34:00 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-15 01:34:00 (8454) [INFO] error    : Corrupt
* 2024-11-15 01:34:00 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-15 01:34:00 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-15 01:34:00 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-15 01:34:00 (8454) [INFO] error    : Corrupt
* 2024-11-15 01:34:00 (8454) [INFO] motopart_production.payment_status
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-15 01:34:00 (8454) [INFO] motopart_production.users
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-15 01:34:00 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-15 01:34:00 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 01:34:00 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-15 01:34:00 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 01:34:00 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-15 01:34:00 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 01:34:00 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-15 01:34:00 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 01:34:00 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-15 01:34:00 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 01:34:00 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-15 01:34:00 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 01:34:00 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-15 01:34:00 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-15 01:34:00 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-15 01:34:00 (8454) [INFO] error    : Corrupt
* 2024-11-15 01:34:00 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-15 01:34:00 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-15 01:34:00 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-15 01:34:00 (8454) [INFO] error    : Corrupt
* 2024-11-15 01:34:00 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-15 01:34:00 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-15 01:34:00 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-15 01:34:00 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-15 01:34:00 (8454) [INFO] error    : Corrupt
* 2024-11-15 01:34:00 (8471) [INFO] 
* 2024-11-15 01:34:00 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-15 01:34:00 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-15 01:34:00 (8441) [INFO] 
* 2024-11-15 01:34:06 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-15 01:34:06 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-15 01:34:06 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-15 01:34:06 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-15 01:34:06 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-15 01:34:06 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-15 01:34:06 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-15 01:34:06 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-15 01:34:06 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-15 01:34:06 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-15 01:34:06 (8441) [INFO] 
* 2024-11-15 01:34:06 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 01:34:06 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-15 01:34:07 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-15 01:34:07 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-15 01:34:07 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-15 01:34:07 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-15 01:34:07 (8454) [INFO]  * remi-php72: rpms.remirepo.net
* 2024-11-15 01:34:07 (8454) [INFO]  * remi-php73: rpms.remirepo.net
* 2024-11-15 01:34:07 (8454) [INFO]  * remi-safe: rpms.remirepo.net
* 2024-11-15 01:34:10 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-15 01:34:10 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-15 01:34:10 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-15 01:34:10 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-15 01:34:10 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-15 01:34:10 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-15 01:34:10 (8454) [INFO] Trying other mirror.
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-15 01:34:10 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 01:34:10 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 01:34:10 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-15 01:34:10 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-15 01:34:10 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-15 01:34:10 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 01:34:10 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-15 01:34:10 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-15 01:34:10 (8454) [INFO]         or
* 2024-11-15 01:34:10 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 01:34:10 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 01:34:10 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 01:34:10 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 01:34:10 (8454) [INFO]         compromise:
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-15 01:34:10 (8454) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-15 01:34:10 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-15 01:34:10 (8471) [INFO] 
* 2024-11-15 01:34:10 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-15 01:34:10 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-15 01:34:10 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-15 01:34:10 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-15 01:34:10 (8441) [INFO] 
* 2024-11-15 01:34:11 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 01:34:11 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-15 01:34:11 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-15 01:34:11 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-15 01:34:11 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-15 01:34:11 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-15 01:34:11 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-15 01:34:11 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-15 01:34:11 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-15 01:34:11 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-15 01:34:11 (8454) [INFO]               : yarn
* 2024-11-15 01:34:11 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-15 01:34:11 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-15 01:34:11 (8471) [INFO] 
* 2024-11-15 01:34:11 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-15 01:34:11 (8441) [INFO] 
* 2024-11-15 01:34:11 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 01:34:11 (8454) [INFO] Determining fastest mirrors
* 2024-11-15 01:34:15 (8454) [INFO]  * EA4: 63.247.64.58
* 2024-11-15 01:34:15 (8454) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-15 01:34:15 (8454) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-15 01:34:15 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-15 01:34:15 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-15 01:34:15 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-15 01:34:15 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-15 01:34:18 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-15 01:34:18 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-15 01:34:18 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-15 01:34:18 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-15 01:34:18 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-15 01:34:18 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-15 01:34:18 (8454) [INFO] Trying other mirror.
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-15 01:34:18 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 01:34:18 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 01:34:18 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-15 01:34:18 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-15 01:34:18 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-15 01:34:18 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 01:34:18 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-15 01:34:18 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-15 01:34:18 (8454) [INFO]         or
* 2024-11-15 01:34:18 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 01:34:18 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 01:34:18 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 01:34:18 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 01:34:18 (8454) [INFO]         compromise:
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-15 01:34:18 (8454) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-15 01:34:18 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-15 01:34:18 (8471) [INFO] 
* 2024-11-15 01:34:18 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-15 01:34:18 (5517) [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-11-15 01:34:18 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-15 01:34:19 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-15 01:34:20 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uzuMtig6D2/ea_profile.json
* 2024-11-15 01:34:24 (475) [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/uzuMtig6D2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-15 01:34:24 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-16 01:34:23 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-16 01:34:23 (9513) [INFO] Script is up to date.
* 2024-11-16 01:34:24 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-16 01:34:24 (5931) [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-11-16 01:34:24 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-16 01:34:24 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-16 01:34:24 (8441) [INFO] 
* 2024-11-16 01:34:29 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-16 01:34:29 (3717) [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.

* 2024-11-16 01:34:29 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-16 01:34:29 (8441) [INFO] 
* 2024-11-16 01:34:44 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-16 01:34:44 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-16 01:34:44 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-16 01:34:44 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-16 01:34:44 (8454) [INFO] error    : Corrupt
* 2024-11-16 01:34:44 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-16 01:34:44 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-16 01:34:44 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-16 01:34:44 (8454) [INFO] error    : Corrupt
* 2024-11-16 01:34:44 (8454) [INFO] motopart_production.payment_status
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-16 01:34:44 (8454) [INFO] motopart_production.users
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-16 01:34:44 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-16 01:34:44 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 01:34:44 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-16 01:34:44 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 01:34:44 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-16 01:34:44 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 01:34:44 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-16 01:34:44 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 01:34:44 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-16 01:34:44 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 01:34:44 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-16 01:34:44 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 01:34:44 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-16 01:34:44 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-16 01:34:44 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-16 01:34:44 (8454) [INFO] error    : Corrupt
* 2024-11-16 01:34:44 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-16 01:34:44 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-16 01:34:44 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-16 01:34:44 (8454) [INFO] error    : Corrupt
* 2024-11-16 01:34:44 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-16 01:34:44 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-16 01:34:44 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-16 01:34:44 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-16 01:34:44 (8454) [INFO] error    : Corrupt
* 2024-11-16 01:34:44 (8471) [INFO] 
* 2024-11-16 01:34:44 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-16 01:34:44 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-16 01:34:44 (8441) [INFO] 
* 2024-11-16 01:34:50 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-16 01:34:50 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-16 01:34:50 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-16 01:34:50 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-16 01:34:50 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-16 01:34:50 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-16 01:34:50 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-16 01:34:50 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-16 01:34:50 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-16 01:34:50 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-16 01:34:50 (8441) [INFO] 
* 2024-11-16 01:34:50 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 01:34:50 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-16 01:34:52 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-16 01:34:52 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-16 01:34:52 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-16 01:34:52 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-16 01:34:52 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-16 01:34:52 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-16 01:34:52 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-16 01:34:55 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-16 01:34:55 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-16 01:34:55 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-16 01:34:55 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-16 01:34:55 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-16 01:34:55 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-16 01:34:55 (8454) [INFO] Trying other mirror.
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-16 01:34:55 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 01:34:55 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 01:34:55 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-16 01:34:55 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-16 01:34:55 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-16 01:34:55 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 01:34:55 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-16 01:34:55 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-16 01:34:55 (8454) [INFO]         or
* 2024-11-16 01:34:55 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 01:34:55 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 01:34:55 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 01:34:55 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 01:34:55 (8454) [INFO]         compromise:
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-16 01:34:55 (8454) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-16 01:34:55 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-16 01:34:55 (8471) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-16 01:34:55 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-16 01:34:55 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-16 01:34:55 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-16 01:34:55 (8441) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 01:34:55 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-16 01:34:55 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-16 01:34:55 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-16 01:34:55 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-16 01:34:55 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-16 01:34:55 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-16 01:34:55 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-16 01:34:55 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-16 01:34:55 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-16 01:34:55 (8454) [INFO]               : yarn
* 2024-11-16 01:34:55 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-16 01:34:55 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-16 01:34:55 (8471) [INFO] 
* 2024-11-16 01:34:55 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-16 01:34:55 (8441) [INFO] 
* 2024-11-16 01:34:55 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 01:34:56 (8454) [INFO] Determining fastest mirrors
* 2024-11-16 01:34:59 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-16 01:34:59 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-16 01:34:59 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-16 01:34:59 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-16 01:34:59 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-16 01:34:59 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-16 01:34:59 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-16 01:35:02 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-16 01:35:02 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-16 01:35:02 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-16 01:35:02 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-16 01:35:02 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-16 01:35:02 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-16 01:35:02 (8454) [INFO] Trying other mirror.
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-16 01:35:02 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 01:35:02 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 01:35:02 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-16 01:35:02 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-16 01:35:02 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-16 01:35:02 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 01:35:02 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-16 01:35:02 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-16 01:35:02 (8454) [INFO]         or
* 2024-11-16 01:35:02 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 01:35:02 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 01:35:02 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 01:35:02 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 01:35:02 (8454) [INFO]         compromise:
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-16 01:35:02 (8454) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-16 01:35:02 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-16 01:35:02 (8471) [INFO] 
* 2024-11-16 01:35:02 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-16 01:35:02 (5517) [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-11-16 01:35:02 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-16 01:35:02 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-16 01:35:04 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zL0LYBOsG1/ea_profile.json
* 2024-11-16 01:35:09 (475) [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/zL0LYBOsG1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-16 01:35:09 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-17 01:34:01 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-17 01:34:01 (9513) [INFO] Script is up to date.
* 2024-11-17 01:34:03 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-17 01:34:03 (5931) [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-11-17 01:34:03 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-17 01:34:03 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-17 01:34:03 (8441) [INFO] 
* 2024-11-17 01:34:08 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-17 01:34:08 (3717) [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.

* 2024-11-17 01:34:08 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-17 01:34:08 (8441) [INFO] 
* 2024-11-17 01:34:22 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-17 01:34:22 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-17 01:34:22 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-17 01:34:22 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-17 01:34:22 (8454) [INFO] error    : Corrupt
* 2024-11-17 01:34:22 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-17 01:34:22 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-17 01:34:22 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-17 01:34:22 (8454) [INFO] error    : Corrupt
* 2024-11-17 01:34:22 (8454) [INFO] motopart_production.payment_status
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-17 01:34:22 (8454) [INFO] motopart_production.users
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-17 01:34:22 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-17 01:34:22 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 01:34:22 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-17 01:34:22 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 01:34:22 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-17 01:34:22 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 01:34:22 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-17 01:34:22 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 01:34:22 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-17 01:34:22 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 01:34:22 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-17 01:34:22 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 01:34:22 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-17 01:34:22 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-17 01:34:22 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-17 01:34:22 (8454) [INFO] error    : Corrupt
* 2024-11-17 01:34:22 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-17 01:34:22 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-17 01:34:22 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-17 01:34:22 (8454) [INFO] error    : Corrupt
* 2024-11-17 01:34:22 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-17 01:34:22 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-17 01:34:22 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-17 01:34:22 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-17 01:34:22 (8454) [INFO] error    : Corrupt
* 2024-11-17 01:34:22 (8471) [INFO] 
* 2024-11-17 01:34:22 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-17 01:34:22 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-17 01:34:22 (8441) [INFO] 
* 2024-11-17 01:34:29 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-17 01:34:29 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-17 01:34:29 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-17 01:34:29 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-17 01:34:29 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-17 01:34:29 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-17 01:34:29 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-17 01:34:29 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-17 01:34:29 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-17 01:34:29 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-17 01:34:29 (8441) [INFO] 
* 2024-11-17 01:34:29 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 01:34:29 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-17 01:34:30 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-17 01:34:30 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-17 01:34:30 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-17 01:34:30 (8454) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-17 01:34:30 (8454) [INFO]  * remi-php72: rpms.remirepo.net
* 2024-11-17 01:34:30 (8454) [INFO]  * remi-php73: rpms.remirepo.net
* 2024-11-17 01:34:30 (8454) [INFO]  * remi-safe: rpms.remirepo.net
* 2024-11-17 01:34:33 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-17 01:34:33 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-17 01:34:33 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-17 01:34:33 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-17 01:34:33 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-17 01:34:33 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-17 01:34:33 (8454) [INFO] Trying other mirror.
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-17 01:34:33 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 01:34:33 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 01:34:33 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-17 01:34:33 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-17 01:34:33 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-17 01:34:33 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 01:34:33 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-17 01:34:33 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-17 01:34:33 (8454) [INFO]         or
* 2024-11-17 01:34:33 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 01:34:33 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 01:34:33 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 01:34:33 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 01:34:33 (8454) [INFO]         compromise:
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-17 01:34:33 (8454) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-17 01:34:33 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-17 01:34:33 (8471) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-17 01:34:33 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-17 01:34:33 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-17 01:34:33 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-17 01:34:33 (8441) [INFO] 
* 2024-11-17 01:34:33 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 01:34:33 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-17 01:34:33 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-17 01:34:33 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-17 01:34:33 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-17 01:34:33 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-17 01:34:33 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-17 01:34:33 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-17 01:34:33 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-17 01:34:33 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-17 01:34:33 (8454) [INFO]               : yarn
* 2024-11-17 01:34:33 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-17 01:34:33 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-17 01:34:33 (8471) [INFO] 
* 2024-11-17 01:34:33 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-17 01:34:33 (8441) [INFO] 
* 2024-11-17 01:34:34 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 01:34:34 (8454) [INFO] Determining fastest mirrors
* 2024-11-17 01:34:37 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-17 01:34:37 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-17 01:34:37 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-17 01:34:37 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-17 01:34:37 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-17 01:34:37 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-17 01:34:37 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-17 01:34:40 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-17 01:34:40 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-17 01:34:40 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-17 01:34:40 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-17 01:34:40 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-17 01:34:40 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-17 01:34:40 (8454) [INFO] Trying other mirror.
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-17 01:34:40 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 01:34:40 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 01:34:40 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-17 01:34:40 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-17 01:34:40 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-17 01:34:40 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 01:34:40 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-17 01:34:40 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-17 01:34:40 (8454) [INFO]         or
* 2024-11-17 01:34:40 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 01:34:40 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 01:34:40 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 01:34:40 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 01:34:40 (8454) [INFO]         compromise:
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-17 01:34:40 (8454) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-17 01:34:40 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-17 01:34:40 (8471) [INFO] 
* 2024-11-17 01:34:40 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-17 01:34:40 (5517) [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-11-17 01:34:40 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-17 01:34:40 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-17 01:34:41 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7n1KdK57m_/ea_profile.json
* 2024-11-17 01:34:47 (475) [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/7n1KdK57m_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-17 01:34:47 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-18 01:33:29 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-18 01:33:29 (9513) [INFO] Script is up to date.
* 2024-11-18 01:33:30 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-18 01:33:30 (5931) [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-11-18 01:33:30 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-18 01:33:30 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-18 01:33:30 (8441) [INFO] 
* 2024-11-18 01:33:34 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-18 01:33:34 (3717) [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.

* 2024-11-18 01:33:34 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-18 01:33:34 (8441) [INFO] 
* 2024-11-18 01:33:53 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-18 01:33:53 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-18 01:33:53 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-18 01:33:53 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-18 01:33:53 (8454) [INFO] error    : Corrupt
* 2024-11-18 01:33:53 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-18 01:33:53 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-18 01:33:53 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-18 01:33:53 (8454) [INFO] error    : Corrupt
* 2024-11-18 01:33:53 (8454) [INFO] motopart_production.payment_status
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-18 01:33:53 (8454) [INFO] motopart_production.users
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-18 01:33:53 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-18 01:33:53 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 01:33:53 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-18 01:33:53 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 01:33:53 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-18 01:33:53 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 01:33:53 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-18 01:33:53 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 01:33:53 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-18 01:33:53 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 01:33:53 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-18 01:33:53 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 01:33:53 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-18 01:33:53 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-18 01:33:53 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-18 01:33:53 (8454) [INFO] error    : Corrupt
* 2024-11-18 01:33:53 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-18 01:33:53 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-18 01:33:53 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-18 01:33:53 (8454) [INFO] error    : Corrupt
* 2024-11-18 01:33:53 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-18 01:33:53 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-18 01:33:53 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-18 01:33:53 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-18 01:33:53 (8454) [INFO] error    : Corrupt
* 2024-11-18 01:33:53 (8471) [INFO] 
* 2024-11-18 01:33:53 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-18 01:33:53 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-18 01:33:53 (8441) [INFO] 
* 2024-11-18 01:34:00 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-18 01:34:00 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-18 01:34:00 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-18 01:34:00 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-18 01:34:00 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-18 01:34:00 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-18 01:34:00 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-18 01:34:00 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-18 01:34:00 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-18 01:34:00 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-18 01:34:00 (8441) [INFO] 
* 2024-11-18 01:34:00 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 01:34:00 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-18 01:34:02 (8454) [INFO]  * EA4: 63.247.64.58
* 2024-11-18 01:34:02 (8454) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-18 01:34:02 (8454) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-18 01:34:02 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-18 01:34:02 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-18 01:34:02 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-18 01:34:02 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-18 01:34:04 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-18 01:34:04 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-18 01:34:04 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-18 01:34:04 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-18 01:34:04 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-18 01:34:04 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-18 01:34:04 (8454) [INFO] Trying other mirror.
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-18 01:34:04 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 01:34:04 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 01:34:04 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-18 01:34:04 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-18 01:34:04 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-18 01:34:04 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 01:34:04 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-18 01:34:04 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-18 01:34:04 (8454) [INFO]         or
* 2024-11-18 01:34:04 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 01:34:04 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 01:34:04 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 01:34:04 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 01:34:04 (8454) [INFO]         compromise:
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-18 01:34:04 (8454) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-18 01:34:04 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-18 01:34:04 (8471) [INFO] 
* 2024-11-18 01:34:04 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-18 01:34:04 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-18 01:34:04 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-18 01:34:04 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-18 01:34:04 (8441) [INFO] 
* 2024-11-18 01:34:05 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 01:34:05 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-18 01:34:05 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-18 01:34:05 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-18 01:34:05 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-18 01:34:05 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-18 01:34:05 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-18 01:34:05 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-18 01:34:05 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-18 01:34:05 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-18 01:34:05 (8454) [INFO]               : yarn
* 2024-11-18 01:34:05 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-18 01:34:05 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-18 01:34:05 (8471) [INFO] 
* 2024-11-18 01:34:05 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-18 01:34:05 (8441) [INFO] 
* 2024-11-18 01:34:05 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 01:34:06 (8454) [INFO] Determining fastest mirrors
* 2024-11-18 01:34:08 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-18 01:34:08 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-18 01:34:08 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-18 01:34:08 (8454) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-18 01:34:08 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-18 01:34:08 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-18 01:34:08 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-18 01:34:11 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-18 01:34:11 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-18 01:34:11 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-18 01:34:11 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-18 01:34:11 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-18 01:34:11 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-18 01:34:11 (8454) [INFO] Trying other mirror.
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-18 01:34:11 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 01:34:11 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 01:34:11 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-18 01:34:11 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-18 01:34:11 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-18 01:34:11 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 01:34:11 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-18 01:34:11 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-18 01:34:11 (8454) [INFO]         or
* 2024-11-18 01:34:11 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 01:34:11 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 01:34:11 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 01:34:11 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 01:34:11 (8454) [INFO]         compromise:
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-18 01:34:11 (8454) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-18 01:34:11 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-18 01:34:11 (8471) [INFO] 
* 2024-11-18 01:34:11 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-18 01:34:11 (5517) [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-11-18 01:34:11 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-18 01:34:11 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-18 01:34:13 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d0z64XNxFs/ea_profile.json
* 2024-11-18 01:34:18 (475) [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/d0z64XNxFs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-18 01:34:18 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-19 01:33:32 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-19 01:33:32 (9513) [INFO] Script is up to date.
* 2024-11-19 01:33:33 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-19 01:33:33 (5931) [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-11-19 01:33:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-19 01:33:33 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-19 01:33:33 (8441) [INFO] 
* 2024-11-19 01:33:37 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-19 01:33:37 (3717) [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.

* 2024-11-19 01:33:37 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-19 01:33:37 (8441) [INFO] 
* 2024-11-19 01:33:48 (8454) [INFO] motopart_oc2.oc_address
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-19 01:33:48 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-19 01:33:48 (8454) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-19 01:33:48 (8454) [INFO] error    : Found 817 keys of 816
* 2024-11-19 01:33:48 (8454) [INFO] error    : Corrupt
* 2024-11-19 01:33:48 (8454) [INFO] motopart_oc2.oc_customer_login
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-19 01:33:48 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-19 01:33:48 (8454) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-19 01:33:48 (8454) [INFO] error    : Corrupt
* 2024-11-19 01:33:48 (8454) [INFO] motopart_production.payment_status
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-19 01:33:48 (8454) [INFO] motopart_production.users
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-19 01:33:48 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-19 01:33:48 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 01:33:48 (8454) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-19 01:33:48 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 01:33:48 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-19 01:33:48 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 01:33:48 (8454) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-19 01:33:48 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 01:33:48 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-19 01:33:48 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 01:33:48 (8454) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-19 01:33:48 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 01:33:48 (8454) [INFO] optisoft_blog.wp_comments
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-19 01:33:48 (8454) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-19 01:33:48 (8454) [INFO] error    : Found 158 keys of 157
* 2024-11-19 01:33:48 (8454) [INFO] error    : Corrupt
* 2024-11-19 01:33:48 (8454) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-19 01:33:48 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-19 01:33:48 (8454) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-19 01:33:48 (8454) [INFO] error    : Corrupt
* 2024-11-19 01:33:48 (8454) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-19 01:33:48 (8454) [INFO] warning  : Table is marked as crashed
* 2024-11-19 01:33:48 (8454) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-19 01:33:48 (8454) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-19 01:33:48 (8454) [INFO] error    : Corrupt
* 2024-11-19 01:33:48 (8471) [INFO] 
* 2024-11-19 01:33:48 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-19 01:33:48 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-19 01:33:48 (8441) [INFO] 
* 2024-11-19 01:33:56 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-19 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-19 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-19 01:33:56 (5624) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-19 01:33:56 (5624) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-19 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-19 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-19 01:33:56 (5624) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-19 01:33:56 (5648) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-19 01:33:56 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-19 01:33:56 (8441) [INFO] 
* 2024-11-19 01:33:56 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 01:33:56 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-19 01:33:58 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-19 01:33:58 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-19 01:33:58 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-19 01:33:58 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-19 01:33:58 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-19 01:33:58 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-19 01:33:58 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-19 01:34:01 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-19 01:34:01 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-19 01:34:01 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-19 01:34:01 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-19 01:34:01 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-19 01:34:01 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-19 01:34:01 (8454) [INFO] Trying other mirror.
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-19 01:34:01 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 01:34:01 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 01:34:01 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-19 01:34:01 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-19 01:34:01 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-19 01:34:01 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 01:34:01 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-19 01:34:01 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-19 01:34:01 (8454) [INFO]         or
* 2024-11-19 01:34:01 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 01:34:01 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 01:34:01 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 01:34:01 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 01:34:01 (8454) [INFO]         compromise:
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-19 01:34:01 (8454) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-19 01:34:01 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-19 01:34:01 (8471) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-19 01:34:01 (5507) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-19 01:34:01 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-19 01:34:01 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-19 01:34:01 (8441) [INFO] 
* 2024-11-19 01:34:01 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 01:34:01 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-19 01:34:01 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-19 01:34:01 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-19 01:34:01 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-19 01:34:01 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-19 01:34:01 (8454) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-19 01:34:01 (8454) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-19 01:34:01 (8454) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-19 01:34:01 (8454) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-19 01:34:01 (8454) [INFO]               : yarn
* 2024-11-19 01:34:01 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-19 01:34:01 (8454) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-19 01:34:01 (8471) [INFO] 
* 2024-11-19 01:34:01 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-19 01:34:01 (8441) [INFO] 
* 2024-11-19 01:34:02 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 01:34:02 (8454) [INFO] Determining fastest mirrors
* 2024-11-19 01:34:06 (8454) [INFO]  * EA4: 185.125.185.32
* 2024-11-19 01:34:06 (8454) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-19 01:34:06 (8454) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-19 01:34:06 (8454) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-19 01:34:06 (8454) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-19 01:34:06 (8454) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-19 01:34:06 (8454) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-19 01:34:09 (8454) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-19 01:34:09 (8454) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-19 01:34:09 (8454) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-19 01:34:09 (8454) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-19 01:34:09 (8454) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-19 01:34:09 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-19 01:34:09 (8454) [INFO] Trying other mirror.
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-19 01:34:09 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 01:34:09 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 01:34:09 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-19 01:34:09 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-19 01:34:09 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-19 01:34:09 (8454) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 01:34:09 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-19 01:34:09 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-19 01:34:09 (8454) [INFO]         or
* 2024-11-19 01:34:09 (8454) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 01:34:09 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 01:34:09 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 01:34:09 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 01:34:09 (8454) [INFO]         compromise:
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-19 01:34:09 (8454) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-19 01:34:09 (8454) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-19 01:34:09 (8471) [INFO] 
* 2024-11-19 01:34:09 (8454) [INFO] Is this ok [y/N]: 
* 2024-11-19 01:34:09 (5517) [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-11-19 01:34:09 (5518) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-19 01:34:09 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-19 01:34:11 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cB3SRY92Vn/ea_profile.json
* 2024-11-19 01:34:15 (475) [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/cB3SRY92Vn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-19 01:34:15 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-20 01:33:29 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-20 01:33:29 (9496) [INFO] Newer version of script found. Downloading.
* 2024-11-20 01:33:30 (9505) [INFO] Script update to version 58 successful.
* 2024-11-20 01:33:31 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-20 01:33:31 (5935) [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-11-20 01:33:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-20 01:33:31 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-20 01:33:31 (8445) [INFO] 
* 2024-11-20 01:33:36 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-20 01:33:36 (3717) [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.

* 2024-11-20 01:33:36 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-20 01:33:36 (8445) [INFO] 
* 2024-11-20 01:33:47 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-20 01:33:47 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-20 01:33:47 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-20 01:33:47 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-20 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-20 01:33:47 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-20 01:33:47 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-20 01:33:47 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-20 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-20 01:33:47 (8458) [INFO] motopart_production.payment_status
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-20 01:33:47 (8458) [INFO] motopart_production.users
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-20 01:33:47 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-20 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 01:33:47 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-20 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 01:33:47 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-20 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 01:33:47 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-20 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 01:33:47 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-20 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 01:33:47 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-20 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 01:33:47 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-20 01:33:47 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-20 01:33:47 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-20 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-20 01:33:47 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-20 01:33:47 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-20 01:33:47 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-20 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-20 01:33:47 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-20 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-20 01:33:47 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-20 01:33:47 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-20 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-20 01:33:47 (8475) [INFO] 
* 2024-11-20 01:33:47 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-20 01:33:47 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-20 01:33:47 (8445) [INFO] 
* 2024-11-20 01:33:53 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-20 01:33:53 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-20 01:33:53 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-20 01:33:53 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-20 01:33:53 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-20 01:33:53 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-20 01:33:53 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-20 01:33:53 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-20 01:33:53 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-20 01:33:53 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 01:33:53 (8445) [INFO] 
* 2024-11-20 01:33:54 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 01:33:54 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-20 01:33:55 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-20 01:33:55 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-20 01:33:55 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-20 01:33:55 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-20 01:33:55 (8458) [INFO]  * remi-php72: mirror.team-cymru.com
* 2024-11-20 01:33:55 (8458) [INFO]  * remi-php73: mirror.team-cymru.com
* 2024-11-20 01:33:55 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-20 01:33:59 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-20 01:33:59 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-20 01:33:59 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-20 01:33:59 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-20 01:33:59 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-20 01:33:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-20 01:33:59 (8458) [INFO] Trying other mirror.
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-20 01:33:59 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 01:33:59 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 01:33:59 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 01:33:59 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 01:33:59 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 01:33:59 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 01:33:59 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 01:33:59 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-20 01:33:59 (8458) [INFO]         or
* 2024-11-20 01:33:59 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 01:33:59 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 01:33:59 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 01:33:59 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 01:33:59 (8458) [INFO]         compromise:
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-20 01:33:59 (8458) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-20 01:33:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-20 01:33:59 (8475) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-20 01:33:59 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-20 01:33:59 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-20 01:33:59 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-20 01:33:59 (8445) [INFO] 
* 2024-11-20 01:33:59 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 01:34:00 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-20 01:34:00 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-20 01:34:00 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-20 01:34:00 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-20 01:34:00 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-20 01:34:00 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-20 01:34:00 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-20 01:34:00 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-20 01:34:00 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-20 01:34:00 (8458) [INFO]               : yarn
* 2024-11-20 01:34:00 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-20 01:34:00 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-20 01:34:00 (8475) [INFO] 
* 2024-11-20 01:34:00 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 01:34:00 (8445) [INFO] 
* 2024-11-20 01:34:00 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 01:34:00 (8458) [INFO] Determining fastest mirrors
* 2024-11-20 01:34:04 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-20 01:34:04 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-20 01:34:04 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-20 01:34:04 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-20 01:34:04 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-20 01:34:04 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-20 01:34:04 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-20 01:34:08 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-20 01:34:08 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-20 01:34:08 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-20 01:34:08 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-20 01:34:08 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-20 01:34:08 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-20 01:34:08 (8458) [INFO] Trying other mirror.
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-20 01:34:08 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 01:34:08 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 01:34:08 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 01:34:08 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 01:34:08 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 01:34:08 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 01:34:08 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 01:34:08 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-20 01:34:08 (8458) [INFO]         or
* 2024-11-20 01:34:08 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 01:34:08 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 01:34:08 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 01:34:08 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 01:34:08 (8458) [INFO]         compromise:
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-20 01:34:08 (8458) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-20 01:34:08 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-20 01:34:08 (8475) [INFO] 
* 2024-11-20 01:34:08 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-20 01:34:08 (5520) [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-11-20 01:34:08 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-20 01:34:09 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-20 01:34:10 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IyYAqEj98L/ea_profile.json
* 2024-11-20 01:34:15 (475) [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/IyYAqEj98L/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-20 01:34:15 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-21 00:27:30 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-21 00:27:30 (9517) [INFO] Script is up to date.
* 2024-11-21 00:27:31 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-21 00:27:31 (5935) [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-11-21 00:27:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-21 00:27:31 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-21 00:27:31 (8445) [INFO] 
* 2024-11-21 00:27:36 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-21 00:27:36 (3717) [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.

* 2024-11-21 00:27:36 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-21 00:27:36 (8445) [INFO] 
* 2024-11-21 00:27:48 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 00:27:48 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-21 00:27:48 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-21 00:27:48 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-21 00:27:48 (8458) [INFO] error    : Corrupt
* 2024-11-21 00:27:48 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 00:27:48 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-21 00:27:48 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-21 00:27:48 (8458) [INFO] error    : Corrupt
* 2024-11-21 00:27:48 (8458) [INFO] motopart_production.payment_status
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-21 00:27:48 (8458) [INFO] motopart_production.users
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-21 00:27:48 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-21 00:27:48 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 00:27:48 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-21 00:27:48 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 00:27:48 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-21 00:27:48 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 00:27:48 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-21 00:27:48 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 00:27:48 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-21 00:27:48 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 00:27:48 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-21 00:27:48 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 00:27:48 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 00:27:48 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-21 00:27:48 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-21 00:27:48 (8458) [INFO] error    : Corrupt
* 2024-11-21 00:27:48 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 00:27:48 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-21 00:27:48 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-21 00:27:48 (8458) [INFO] error    : Corrupt
* 2024-11-21 00:27:48 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-21 00:27:48 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 00:27:48 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-21 00:27:48 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-21 00:27:48 (8458) [INFO] error    : Corrupt
* 2024-11-21 00:27:48 (8475) [INFO] 
* 2024-11-21 00:27:48 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-21 00:27:48 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-21 00:27:48 (8445) [INFO] 
* 2024-11-21 00:28:10 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-21 00:28:10 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-21 00:28:10 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-21 00:28:10 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-21 00:28:10 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-21 00:28:10 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-21 00:28:10 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-21 00:28:10 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-21 00:28:10 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-21 00:28:10 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 00:28:10 (8445) [INFO] 
* 2024-11-21 00:28:10 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 00:28:10 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-21 00:28:12 (8458) [INFO]  * EA4: 63.247.64.58
* 2024-11-21 00:28:12 (8458) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-21 00:28:12 (8458) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-21 00:28:12 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-21 00:28:12 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-21 00:28:12 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-21 00:28:12 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-21 00:28:18 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 00:28:18 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-21 00:28:18 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-21 00:28:18 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-21 00:28:18 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 00:28:18 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 00:28:18 (8458) [INFO] Trying other mirror.
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-21 00:28:18 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 00:28:18 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 00:28:18 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 00:28:18 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 00:28:18 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 00:28:18 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 00:28:18 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 00:28:18 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-21 00:28:18 (8458) [INFO]         or
* 2024-11-21 00:28:18 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 00:28:18 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 00:28:18 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 00:28:18 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 00:28:18 (8458) [INFO]         compromise:
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-21 00:28:18 (8458) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-21 00:28:18 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 00:28:18 (8475) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-21 00:28:18 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 00:28:18 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-21 00:28:18 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-21 00:28:18 (8445) [INFO] 
* 2024-11-21 00:28:18 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 00:28:19 (8458) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 164985.
* 2024-11-21 00:28:19 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:19 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:19 (8458) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-11-21 00:28:19 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:23 ago
* 2024-11-21 00:28:19 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:21 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:21 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:21 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:21 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:25 ago
* 2024-11-21 00:28:21 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:23 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:23 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:23 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:23 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:27 ago
* 2024-11-21 00:28:23 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:25 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:25 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:25 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:25 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:29 ago
* 2024-11-21 00:28:25 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:27 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:27 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:27 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:27 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:31 ago
* 2024-11-21 00:28:27 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:29 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:29 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:29 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:29 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:33 ago
* 2024-11-21 00:28:29 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:31 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:31 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:31 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:31 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:35 ago
* 2024-11-21 00:28:31 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:33 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:33 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:33 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:33 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:37 ago
* 2024-11-21 00:28:33 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:35 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:35 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:35 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:35 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:39 ago
* 2024-11-21 00:28:35 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:37 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:37 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:37 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:37 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:41 ago
* 2024-11-21 00:28:37 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:39 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:39 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:39 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:39 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:43 ago
* 2024-11-21 00:28:39 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:41 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:41 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:41 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:41 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:45 ago
* 2024-11-21 00:28:41 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:43 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:43 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:43 (8458) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-11-21 00:28:43 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:47 ago
* 2024-11-21 00:28:43 (8458) [INFO]     State  : Sleeping, pid: 164985
* 2024-11-21 00:28:45 (8458) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-11-21 00:28:45 (8458) [INFO]   The other application is: yum
* 2024-11-21 00:28:45 (8458) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-11-21 00:28:45 (8458) [INFO]     Started: Thu Nov 21 00:27:56 2024 - 00:49 ago
* 2024-11-21 00:28:45 (8458) [INFO]     State  : Running, pid: 164985
* 2024-11-21 00:28:47 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-21 00:28:47 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-21 00:28:47 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-21 00:28:47 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-21 00:28:47 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-21 00:28:47 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-21 00:28:47 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-21 00:28:47 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-21 00:28:47 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-21 00:28:47 (8458) [INFO]               : yarn
* 2024-11-21 00:28:47 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-21 00:28:47 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-21 00:28:47 (8475) [INFO] 
* 2024-11-21 00:28:47 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 00:28:47 (8445) [INFO] 
* 2024-11-21 00:28:47 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 00:28:47 (8458) [INFO] Determining fastest mirrors
* 2024-11-21 00:28:50 (8458) [INFO]  * EA4: 63.247.64.58
* 2024-11-21 00:28:50 (8458) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-21 00:28:50 (8458) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-21 00:28:50 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-21 00:28:50 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-21 00:28:50 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-21 00:28:50 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-21 00:29:21 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2024-11-21 00:29:21 (8458) [INFO] Trying other mirror.
* 2024-11-21 00:29:25 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 00:29:25 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-21 00:29:25 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-21 00:29:25 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-21 00:29:25 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 00:29:25 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 00:29:25 (8458) [INFO] Trying other mirror.
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-21 00:29:25 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 00:29:25 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 00:29:25 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 00:29:25 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 00:29:25 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 00:29:25 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 00:29:25 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 00:29:25 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-21 00:29:25 (8458) [INFO]         or
* 2024-11-21 00:29:25 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 00:29:25 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 00:29:25 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 00:29:25 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 00:29:25 (8458) [INFO]         compromise:
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-21 00:29:25 (8458) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-21 00:29:25 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 00:29:25 (8475) [INFO] 
* 2024-11-21 00:29:25 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-21 00:29:25 (5520) [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-11-21 00:29:25 (5521) [ERROR] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 00:29:25 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-21 00:29:27 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/omyYHrXaKJ/ea_profile.json
* 2024-11-21 00:29:34 (475) [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/omyYHrXaKJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-21 00:29:34 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-21 01:35:45 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-21 01:35:45 (9517) [INFO] Script is up to date.
* 2024-11-21 01:35:46 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-21 01:35:46 (5935) [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-11-21 01:35:47 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-21 01:35:47 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-21 01:35:47 (8445) [INFO] 
* 2024-11-21 01:35:52 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-21 01:35:52 (3717) [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.

* 2024-11-21 01:35:52 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-21 01:35:52 (8445) [INFO] 
* 2024-11-21 01:36:01 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 01:36:01 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-21 01:36:01 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-21 01:36:01 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-21 01:36:01 (8458) [INFO] error    : Corrupt
* 2024-11-21 01:36:01 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 01:36:01 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-21 01:36:01 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-21 01:36:01 (8458) [INFO] error    : Corrupt
* 2024-11-21 01:36:01 (8458) [INFO] motopart_production.payment_status
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-21 01:36:01 (8458) [INFO] motopart_production.users
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-21 01:36:01 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-21 01:36:01 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 01:36:01 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-21 01:36:01 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 01:36:01 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-21 01:36:01 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 01:36:01 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-21 01:36:01 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 01:36:01 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-21 01:36:01 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 01:36:01 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-21 01:36:01 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 01:36:01 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 01:36:01 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-21 01:36:01 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-21 01:36:01 (8458) [INFO] error    : Corrupt
* 2024-11-21 01:36:01 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 01:36:01 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-21 01:36:01 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-21 01:36:01 (8458) [INFO] error    : Corrupt
* 2024-11-21 01:36:01 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-21 01:36:01 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-21 01:36:01 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-21 01:36:01 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-21 01:36:01 (8458) [INFO] error    : Corrupt
* 2024-11-21 01:36:01 (8475) [INFO] 
* 2024-11-21 01:36:01 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-21 01:36:01 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-21 01:36:01 (8445) [INFO] 
* 2024-11-21 01:37:18 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-21 01:37:18 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-21 01:37:18 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-21 01:37:18 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-21 01:37:18 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-21 01:37:18 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-21 01:37:18 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-21 01:37:18 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-21 01:37:18 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-21 01:37:18 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 01:37:18 (8445) [INFO] 
* 2024-11-21 01:37:18 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 01:37:18 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-21 01:37:34 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-21 01:37:34 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-21 01:37:34 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-21 01:37:34 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-21 01:37:34 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-21 01:37:34 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-21 01:37:34 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-21 01:37:45 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 01:37:46 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-21 01:37:46 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-21 01:37:46 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-21 01:37:46 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 01:37:46 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 01:37:46 (8458) [INFO] Trying other mirror.
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-21 01:37:46 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 01:37:46 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 01:37:46 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 01:37:46 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 01:37:46 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 01:37:46 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 01:37:46 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 01:37:46 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-21 01:37:46 (8458) [INFO]         or
* 2024-11-21 01:37:46 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 01:37:46 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 01:37:46 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 01:37:46 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 01:37:46 (8458) [INFO]         compromise:
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-21 01:37:46 (8458) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-21 01:37:46 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 01:37:46 (8475) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-21 01:37:46 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 01:37:46 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-21 01:37:46 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-21 01:37:46 (8445) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 01:37:46 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-21 01:37:46 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-21 01:37:46 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-21 01:37:46 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-21 01:37:46 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-21 01:37:46 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-21 01:37:46 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-21 01:37:46 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-21 01:37:46 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-21 01:37:46 (8458) [INFO]               : yarn
* 2024-11-21 01:37:46 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-21 01:37:46 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-21 01:37:46 (8475) [INFO] 
* 2024-11-21 01:37:46 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 01:37:46 (8445) [INFO] 
* 2024-11-21 01:37:46 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 01:37:46 (8458) [INFO] Determining fastest mirrors
* 2024-11-21 01:38:05 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-21 01:38:05 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-21 01:38:05 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-21 01:38:05 (8458) [INFO]  * epel: dl.fedoraproject.org
* 2024-11-21 01:38:05 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-21 01:38:05 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-21 01:38:05 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-21 01:38:13 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 01:38:13 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-21 01:38:13 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-21 01:38:13 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-21 01:38:13 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-21 01:38:13 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 01:38:13 (8458) [INFO] Trying other mirror.
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-21 01:38:13 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 01:38:13 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 01:38:13 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 01:38:13 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 01:38:13 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 01:38:13 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 01:38:13 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 01:38:13 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-21 01:38:13 (8458) [INFO]         or
* 2024-11-21 01:38:13 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 01:38:13 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 01:38:13 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 01:38:13 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 01:38:13 (8458) [INFO]         compromise:
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-21 01:38:13 (8458) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-21 01:38:13 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 01:38:13 (8475) [INFO] 
* 2024-11-21 01:38:13 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-21 01:38:13 (5520) [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-11-21 01:38:13 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-21 01:38:14 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-21 01:38:15 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A4ZnNeTy_m/ea_profile.json
* 2024-11-21 01:38:40 (475) [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/A4ZnNeTy_m/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-21 01:38:40 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-22 01:33:30 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-22 01:33:30 (9517) [INFO] Script is up to date.
* 2024-11-22 01:33:31 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-22 01:33:31 (5935) [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-11-22 01:33:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-22 01:33:31 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-22 01:33:31 (8445) [INFO] 
* 2024-11-22 01:33:35 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-22 01:33:35 (3717) [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.

* 2024-11-22 01:33:35 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-22 01:33:35 (8445) [INFO] 
* 2024-11-22 01:33:47 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-22 01:33:47 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-22 01:33:47 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-22 01:33:47 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-22 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-22 01:33:47 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-22 01:33:47 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-22 01:33:47 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-22 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-22 01:33:47 (8458) [INFO] motopart_production.payment_status
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-22 01:33:47 (8458) [INFO] motopart_production.users
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-22 01:33:47 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-22 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 01:33:47 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-22 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 01:33:47 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-22 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 01:33:47 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-22 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 01:33:47 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-22 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 01:33:47 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-22 01:33:47 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 01:33:47 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-22 01:33:47 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-22 01:33:47 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-22 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-22 01:33:47 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-22 01:33:47 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-22 01:33:47 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-22 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-22 01:33:47 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-22 01:33:47 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-22 01:33:47 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-22 01:33:47 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-22 01:33:47 (8458) [INFO] error    : Corrupt
* 2024-11-22 01:33:47 (8475) [INFO] 
* 2024-11-22 01:33:47 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-22 01:33:47 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-22 01:33:47 (8445) [INFO] 
* 2024-11-22 01:34:08 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-22 01:34:08 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-22 01:34:08 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-22 01:34:08 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-22 01:34:08 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-22 01:34:08 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-22 01:34:08 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-22 01:34:08 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-22 01:34:08 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-22 01:34:08 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-22 01:34:08 (8445) [INFO] 
* 2024-11-22 01:34:08 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 01:34:08 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-22 01:34:09 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-22 01:34:09 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-22 01:34:09 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-22 01:34:09 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-22 01:34:09 (8458) [INFO]  * remi-php72: mirror.team-cymru.com
* 2024-11-22 01:34:09 (8458) [INFO]  * remi-php73: mirror.team-cymru.com
* 2024-11-22 01:34:09 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-22 01:34:12 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-22 01:34:12 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-22 01:34:12 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-22 01:34:12 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-22 01:34:12 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-22 01:34:12 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-22 01:34:12 (8458) [INFO] Trying other mirror.
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-22 01:34:12 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 01:34:12 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 01:34:12 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-22 01:34:12 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-22 01:34:12 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-22 01:34:12 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 01:34:12 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-22 01:34:12 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-22 01:34:12 (8458) [INFO]         or
* 2024-11-22 01:34:12 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 01:34:12 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 01:34:12 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 01:34:12 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 01:34:12 (8458) [INFO]         compromise:
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-22 01:34:12 (8458) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-22 01:34:12 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-22 01:34:12 (8475) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-22 01:34:12 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-22 01:34:12 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-22 01:34:12 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-22 01:34:12 (8445) [INFO] 
* 2024-11-22 01:34:12 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 01:34:13 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-22 01:34:13 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-22 01:34:13 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-22 01:34:13 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-22 01:34:13 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-22 01:34:13 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-22 01:34:13 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-22 01:34:13 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-22 01:34:13 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-22 01:34:13 (8458) [INFO]               : yarn
* 2024-11-22 01:34:13 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-22 01:34:13 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-22 01:34:13 (8475) [INFO] 
* 2024-11-22 01:34:13 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-22 01:34:13 (8445) [INFO] 
* 2024-11-22 01:34:13 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 01:34:13 (8458) [INFO] Determining fastest mirrors
* 2024-11-22 01:34:20 (8458) [INFO]  * EA4: 63.247.64.58
* 2024-11-22 01:34:20 (8458) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-22 01:34:20 (8458) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-22 01:34:20 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-22 01:34:20 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-22 01:34:20 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-22 01:34:20 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-22 01:34:23 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-22 01:34:24 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-22 01:34:24 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-22 01:34:24 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-22 01:34:24 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-22 01:34:24 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-22 01:34:24 (8458) [INFO] Trying other mirror.
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-22 01:34:24 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 01:34:24 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 01:34:24 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-22 01:34:24 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-22 01:34:24 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-22 01:34:24 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 01:34:24 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-22 01:34:24 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-22 01:34:24 (8458) [INFO]         or
* 2024-11-22 01:34:24 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 01:34:24 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 01:34:24 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 01:34:24 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 01:34:24 (8458) [INFO]         compromise:
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-22 01:34:24 (8458) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-22 01:34:24 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-22 01:34:24 (8475) [INFO] 
* 2024-11-22 01:34:24 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-22 01:34:24 (5520) [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-11-22 01:34:24 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-22 01:34:24 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-22 01:34:25 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/e1CIhj5hrV/ea_profile.json
* 2024-11-22 01:34:30 (475) [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/e1CIhj5hrV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-22 01:34:30 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-23 01:34:56 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-23 01:34:56 (9517) [INFO] Script is up to date.
* 2024-11-23 01:34:57 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-23 01:34:57 (5935) [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-11-23 01:34:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-23 01:34:58 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-23 01:34:58 (8445) [INFO] 
* 2024-11-23 01:35:02 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-23 01:35:02 (3717) [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.

* 2024-11-23 01:35:02 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-23 01:35:02 (8445) [INFO] 
* 2024-11-23 01:35:23 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-23 01:35:23 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-23 01:35:23 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-23 01:35:23 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-23 01:35:23 (8458) [INFO] error    : Corrupt
* 2024-11-23 01:35:23 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-23 01:35:23 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-23 01:35:23 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-23 01:35:23 (8458) [INFO] error    : Corrupt
* 2024-11-23 01:35:23 (8458) [INFO] motopart_production.payment_status
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-23 01:35:23 (8458) [INFO] motopart_production.users
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-23 01:35:23 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-23 01:35:23 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 01:35:23 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-23 01:35:23 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 01:35:23 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-23 01:35:23 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 01:35:23 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-23 01:35:23 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 01:35:23 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-23 01:35:23 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 01:35:23 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-23 01:35:23 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 01:35:23 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-23 01:35:23 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-23 01:35:23 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-23 01:35:23 (8458) [INFO] error    : Corrupt
* 2024-11-23 01:35:23 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-23 01:35:23 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-23 01:35:23 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-23 01:35:23 (8458) [INFO] error    : Corrupt
* 2024-11-23 01:35:23 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-23 01:35:23 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-23 01:35:23 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-23 01:35:23 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-23 01:35:23 (8458) [INFO] error    : Corrupt
* 2024-11-23 01:35:23 (8475) [INFO] 
* 2024-11-23 01:35:23 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-23 01:35:23 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-23 01:35:23 (8445) [INFO] 
* 2024-11-23 01:35:30 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-23 01:35:30 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-23 01:35:30 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-23 01:35:30 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-23 01:35:30 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-23 01:35:30 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-23 01:35:30 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-23 01:35:30 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-23 01:35:30 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-23 01:35:30 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-23 01:35:30 (8445) [INFO] 
* 2024-11-23 01:35:30 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 01:35:30 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-23 01:35:33 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-23 01:35:33 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-23 01:35:33 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-23 01:35:33 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-23 01:35:33 (8458) [INFO]  * remi-php72: mirrors.upr.edu
* 2024-11-23 01:35:33 (8458) [INFO]  * remi-php73: mirrors.upr.edu
* 2024-11-23 01:35:33 (8458) [INFO]  * remi-safe: mirrors.upr.edu
* 2024-11-23 01:35:36 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-23 01:35:36 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-23 01:35:36 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-23 01:35:36 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-23 01:35:36 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-23 01:35:36 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-23 01:35:36 (8458) [INFO] Trying other mirror.
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-23 01:35:36 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 01:35:36 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 01:35:36 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-23 01:35:36 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-23 01:35:36 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-23 01:35:36 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 01:35:36 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-23 01:35:36 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-23 01:35:36 (8458) [INFO]         or
* 2024-11-23 01:35:36 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 01:35:36 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 01:35:36 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 01:35:36 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 01:35:36 (8458) [INFO]         compromise:
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-23 01:35:36 (8458) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-23 01:35:36 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-23 01:35:36 (8475) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-23 01:35:36 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-23 01:35:36 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-23 01:35:36 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-23 01:35:36 (8445) [INFO] 
* 2024-11-23 01:35:36 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 01:35:36 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-23 01:35:36 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-23 01:35:36 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-23 01:35:36 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-23 01:35:36 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-23 01:35:36 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-23 01:35:36 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-23 01:35:36 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-23 01:35:36 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-23 01:35:36 (8458) [INFO]               : yarn
* 2024-11-23 01:35:36 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-23 01:35:36 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-23 01:35:36 (8475) [INFO] 
* 2024-11-23 01:35:36 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-23 01:35:36 (8445) [INFO] 
* 2024-11-23 01:35:37 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 01:35:37 (8458) [INFO] Determining fastest mirrors
* 2024-11-23 01:35:40 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-23 01:35:40 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-23 01:35:40 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-23 01:35:40 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-23 01:35:40 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-23 01:35:40 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-23 01:35:40 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-23 01:35:44 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-23 01:35:44 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-23 01:35:44 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-23 01:35:44 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-23 01:35:44 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-23 01:35:44 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-23 01:35:44 (8458) [INFO] Trying other mirror.
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-23 01:35:44 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 01:35:44 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 01:35:44 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-23 01:35:44 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-23 01:35:44 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-23 01:35:44 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 01:35:44 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-23 01:35:44 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-23 01:35:44 (8458) [INFO]         or
* 2024-11-23 01:35:44 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 01:35:44 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 01:35:44 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 01:35:44 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 01:35:44 (8458) [INFO]         compromise:
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-23 01:35:44 (8458) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-23 01:35:44 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-23 01:35:44 (8475) [INFO] 
* 2024-11-23 01:35:44 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-23 01:35:44 (5520) [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-11-23 01:35:44 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-23 01:35:44 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-23 01:35:45 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4DwoZnx4nt/ea_profile.json
* 2024-11-23 01:35:50 (475) [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/4DwoZnx4nt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-23 01:35:50 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-24 01:34:12 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-24 01:34:13 (9517) [INFO] Script is up to date.
* 2024-11-24 01:34:14 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-24 01:34:14 (5935) [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-11-24 01:34:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-24 01:34:14 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-24 01:34:14 (8445) [INFO] 
* 2024-11-24 01:34:20 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-24 01:34:20 (3717) [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.

* 2024-11-24 01:34:20 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-24 01:34:20 (8445) [INFO] 
* 2024-11-24 01:34:41 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-24 01:34:41 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-24 01:34:41 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-24 01:34:41 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-24 01:34:41 (8458) [INFO] error    : Corrupt
* 2024-11-24 01:34:41 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-24 01:34:41 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-24 01:34:41 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-24 01:34:41 (8458) [INFO] error    : Corrupt
* 2024-11-24 01:34:41 (8458) [INFO] motopart_production.payment_status
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-24 01:34:41 (8458) [INFO] motopart_production.users
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-24 01:34:41 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-24 01:34:41 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 01:34:41 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-24 01:34:41 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 01:34:41 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-24 01:34:41 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 01:34:41 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-24 01:34:41 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 01:34:41 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-24 01:34:41 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 01:34:41 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-24 01:34:41 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 01:34:41 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-24 01:34:41 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-24 01:34:41 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-24 01:34:41 (8458) [INFO] error    : Corrupt
* 2024-11-24 01:34:41 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-24 01:34:41 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-24 01:34:41 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-24 01:34:41 (8458) [INFO] error    : Corrupt
* 2024-11-24 01:34:41 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-24 01:34:41 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-24 01:34:41 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-24 01:34:41 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-24 01:34:41 (8458) [INFO] error    : Corrupt
* 2024-11-24 01:34:41 (8475) [INFO] 
* 2024-11-24 01:34:41 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-24 01:34:41 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-24 01:34:41 (8445) [INFO] 
* 2024-11-24 01:34:47 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-24 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-24 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-24 01:34:47 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-24 01:34:47 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-24 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-24 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-24 01:34:47 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-24 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-24 01:34:47 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-24 01:34:47 (8445) [INFO] 
* 2024-11-24 01:34:48 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 01:34:48 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-24 01:34:49 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-24 01:34:49 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-24 01:34:49 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-24 01:34:49 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-24 01:34:49 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-24 01:34:49 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-24 01:34:49 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-24 01:34:53 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-24 01:34:53 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-24 01:34:53 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-24 01:34:53 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-24 01:34:53 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-24 01:34:53 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-24 01:34:53 (8458) [INFO] Trying other mirror.
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-24 01:34:53 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 01:34:53 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 01:34:53 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-24 01:34:53 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-24 01:34:53 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-24 01:34:53 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 01:34:53 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-24 01:34:53 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-24 01:34:53 (8458) [INFO]         or
* 2024-11-24 01:34:53 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 01:34:53 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 01:34:53 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 01:34:53 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 01:34:53 (8458) [INFO]         compromise:
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-24 01:34:53 (8458) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-24 01:34:53 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-24 01:34:53 (8475) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-24 01:34:53 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-24 01:34:53 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-24 01:34:53 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-24 01:34:53 (8445) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 01:34:53 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-24 01:34:53 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-24 01:34:53 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-24 01:34:53 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-24 01:34:53 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-24 01:34:53 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-24 01:34:53 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-24 01:34:53 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-24 01:34:53 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-24 01:34:53 (8458) [INFO]               : yarn
* 2024-11-24 01:34:53 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-24 01:34:53 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-24 01:34:53 (8475) [INFO] 
* 2024-11-24 01:34:53 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-24 01:34:53 (8445) [INFO] 
* 2024-11-24 01:34:53 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 01:34:54 (8458) [INFO] Determining fastest mirrors
* 2024-11-24 01:34:56 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-24 01:34:56 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-24 01:34:56 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-24 01:34:56 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-24 01:34:56 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-24 01:34:56 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-24 01:34:56 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-24 01:35:00 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-24 01:35:00 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-24 01:35:00 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-24 01:35:00 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-24 01:35:00 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-24 01:35:00 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-24 01:35:00 (8458) [INFO] Trying other mirror.
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-24 01:35:00 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 01:35:00 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 01:35:00 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-24 01:35:00 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-24 01:35:00 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-24 01:35:00 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 01:35:00 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-24 01:35:00 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-24 01:35:00 (8458) [INFO]         or
* 2024-11-24 01:35:00 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 01:35:00 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 01:35:00 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 01:35:00 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 01:35:00 (8458) [INFO]         compromise:
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-24 01:35:00 (8458) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-24 01:35:00 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-24 01:35:00 (8475) [INFO] 
* 2024-11-24 01:35:00 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-24 01:35:00 (5520) [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-11-24 01:35:00 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-24 01:35:00 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-24 01:35:01 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iFqpNDGGDr/ea_profile.json
* 2024-11-24 01:35:07 (475) [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/iFqpNDGGDr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-24 01:35:07 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-25 01:33:32 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-25 01:33:32 (9517) [INFO] Script is up to date.
* 2024-11-25 01:33:33 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-25 01:33:33 (5935) [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-11-25 01:33:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-25 01:33:33 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-25 01:33:33 (8445) [INFO] 
* 2024-11-25 01:33:43 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-25 01:33:43 (3717) [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.

* 2024-11-25 01:33:43 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-25 01:33:43 (8445) [INFO] 
* 2024-11-25 01:34:04 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-25 01:34:04 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-25 01:34:04 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-25 01:34:04 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-25 01:34:04 (8458) [INFO] error    : Corrupt
* 2024-11-25 01:34:04 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-25 01:34:04 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-25 01:34:04 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-25 01:34:04 (8458) [INFO] error    : Corrupt
* 2024-11-25 01:34:04 (8458) [INFO] motopart_production.payment_status
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-25 01:34:04 (8458) [INFO] motopart_production.users
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-25 01:34:04 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-25 01:34:04 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 01:34:04 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-25 01:34:04 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 01:34:04 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-25 01:34:04 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 01:34:04 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-25 01:34:04 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 01:34:04 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-25 01:34:04 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 01:34:04 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-25 01:34:04 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 01:34:04 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-25 01:34:04 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-25 01:34:04 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-25 01:34:04 (8458) [INFO] error    : Corrupt
* 2024-11-25 01:34:04 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-25 01:34:04 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-25 01:34:04 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-25 01:34:04 (8458) [INFO] error    : Corrupt
* 2024-11-25 01:34:04 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-25 01:34:04 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-25 01:34:04 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-25 01:34:04 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-25 01:34:04 (8458) [INFO] error    : Corrupt
* 2024-11-25 01:34:04 (8475) [INFO] 
* 2024-11-25 01:34:04 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-25 01:34:04 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-25 01:34:04 (8445) [INFO] 
* 2024-11-25 01:34:17 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-25 01:34:17 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-25 01:34:17 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-25 01:34:17 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-25 01:34:17 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-25 01:34:17 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-25 01:34:17 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-25 01:34:17 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-25 01:34:17 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-25 01:34:17 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-25 01:34:17 (8445) [INFO] 
* 2024-11-25 01:34:17 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 01:34:18 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-25 01:34:20 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-25 01:34:20 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-25 01:34:20 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-25 01:34:20 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-25 01:34:20 (8458) [INFO]  * remi-php72: muug.ca
* 2024-11-25 01:34:20 (8458) [INFO]  * remi-php73: muug.ca
* 2024-11-25 01:34:20 (8458) [INFO]  * remi-safe: muug.ca
* 2024-11-25 01:34:24 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-25 01:34:24 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-25 01:34:24 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-25 01:34:24 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-25 01:34:24 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-25 01:34:24 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-25 01:34:24 (8458) [INFO] Trying other mirror.
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-25 01:34:24 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 01:34:24 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 01:34:24 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-25 01:34:24 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-25 01:34:24 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-25 01:34:24 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 01:34:24 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-25 01:34:24 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-25 01:34:24 (8458) [INFO]         or
* 2024-11-25 01:34:24 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 01:34:24 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 01:34:24 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 01:34:24 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 01:34:24 (8458) [INFO]         compromise:
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-25 01:34:24 (8458) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-25 01:34:24 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-25 01:34:24 (8475) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-25 01:34:24 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-25 01:34:24 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-25 01:34:24 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-25 01:34:24 (8445) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 01:34:24 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-25 01:34:24 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-25 01:34:24 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-25 01:34:24 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-25 01:34:24 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-25 01:34:24 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-25 01:34:24 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-25 01:34:24 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-25 01:34:24 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-25 01:34:24 (8458) [INFO]               : yarn
* 2024-11-25 01:34:24 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-25 01:34:24 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-25 01:34:24 (8475) [INFO] 
* 2024-11-25 01:34:24 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-25 01:34:24 (8445) [INFO] 
* 2024-11-25 01:34:24 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 01:34:25 (8458) [INFO] Determining fastest mirrors
* 2024-11-25 01:34:29 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-25 01:34:29 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-25 01:34:29 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-25 01:34:29 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-11-25 01:34:29 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-25 01:34:29 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-25 01:34:29 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-25 01:34:32 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-25 01:34:32 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-25 01:34:32 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-25 01:34:32 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-25 01:34:32 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-25 01:34:32 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-25 01:34:32 (8458) [INFO] Trying other mirror.
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-25 01:34:32 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 01:34:32 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 01:34:32 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-25 01:34:32 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-25 01:34:32 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-25 01:34:32 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 01:34:32 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-25 01:34:32 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-25 01:34:32 (8458) [INFO]         or
* 2024-11-25 01:34:32 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 01:34:32 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 01:34:32 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 01:34:32 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 01:34:32 (8458) [INFO]         compromise:
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-25 01:34:32 (8458) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-25 01:34:32 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-25 01:34:32 (8475) [INFO] 
* 2024-11-25 01:34:32 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-25 01:34:32 (5520) [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-11-25 01:34:32 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-25 01:34:32 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-25 01:34:34 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8xht7PBQ03/ea_profile.json
* 2024-11-25 01:34:39 (475) [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/8xht7PBQ03/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-25 01:34:39 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-26 01:34:19 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-26 01:34:19 (9517) [INFO] Script is up to date.
* 2024-11-26 01:34:20 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-26 01:34:20 (5935) [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-11-26 01:34:20 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-26 01:34:20 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-26 01:34:20 (8445) [INFO] 
* 2024-11-26 01:34:25 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-26 01:34:25 (3717) [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.

* 2024-11-26 01:34:25 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-26 01:34:25 (8445) [INFO] 
* 2024-11-26 01:34:39 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-26 01:34:39 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-26 01:34:39 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-26 01:34:39 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-26 01:34:39 (8458) [INFO] error    : Corrupt
* 2024-11-26 01:34:39 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-26 01:34:39 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-26 01:34:39 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-26 01:34:39 (8458) [INFO] error    : Corrupt
* 2024-11-26 01:34:39 (8458) [INFO] motopart_production.payment_status
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-26 01:34:39 (8458) [INFO] motopart_production.users
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-26 01:34:39 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-26 01:34:39 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 01:34:39 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-26 01:34:39 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 01:34:39 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-26 01:34:39 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 01:34:39 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-26 01:34:39 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 01:34:39 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-26 01:34:39 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 01:34:39 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-26 01:34:39 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 01:34:39 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-26 01:34:39 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-26 01:34:39 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-26 01:34:39 (8458) [INFO] error    : Corrupt
* 2024-11-26 01:34:39 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-26 01:34:39 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-26 01:34:39 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-26 01:34:39 (8458) [INFO] error    : Corrupt
* 2024-11-26 01:34:39 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-26 01:34:39 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-26 01:34:39 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-26 01:34:39 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-26 01:34:39 (8458) [INFO] error    : Corrupt
* 2024-11-26 01:34:39 (8475) [INFO] 
* 2024-11-26 01:34:39 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-26 01:34:39 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-26 01:34:39 (8445) [INFO] 
* 2024-11-26 01:34:47 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-26 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-26 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-26 01:34:47 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-26 01:34:47 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-26 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-26 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-26 01:34:47 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-26 01:34:47 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-26 01:34:47 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-26 01:34:47 (8445) [INFO] 
* 2024-11-26 01:34:48 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 01:34:48 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-26 01:34:49 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-26 01:34:49 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-26 01:34:49 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-26 01:34:49 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-26 01:34:49 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-26 01:34:49 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-26 01:34:49 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-26 01:34:53 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-26 01:34:53 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-26 01:34:53 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-26 01:34:53 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-26 01:34:53 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-26 01:34:53 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-26 01:34:53 (8458) [INFO] Trying other mirror.
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-26 01:34:53 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-26 01:34:53 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-26 01:34:53 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-26 01:34:53 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-26 01:34:53 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-26 01:34:53 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-26 01:34:53 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-26 01:34:53 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-26 01:34:53 (8458) [INFO]         or
* 2024-11-26 01:34:53 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-26 01:34:53 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-26 01:34:53 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-26 01:34:53 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-26 01:34:53 (8458) [INFO]         compromise:
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-26 01:34:53 (8458) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-26 01:34:53 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-26 01:34:53 (8475) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-26 01:34:53 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-26 01:34:53 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-26 01:34:53 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-26 01:34:53 (8445) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 01:34:53 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-26 01:34:53 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-26 01:34:53 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-26 01:34:53 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-26 01:34:53 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-26 01:34:53 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-26 01:34:53 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-26 01:34:53 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-26 01:34:53 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-26 01:34:53 (8458) [INFO]               : yarn
* 2024-11-26 01:34:53 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-26 01:34:53 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-26 01:34:53 (8475) [INFO] 
* 2024-11-26 01:34:53 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-26 01:34:53 (8445) [INFO] 
* 2024-11-26 01:34:53 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 01:34:54 (8458) [INFO] Determining fastest mirrors
* 2024-11-26 01:34:55 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-26 01:34:55 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-26 01:34:55 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-26 01:34:55 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-26 01:34:55 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-26 01:34:55 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-26 01:34:55 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-26 01:34:59 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-26 01:34:59 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-26 01:34:59 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-26 01:34:59 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-26 01:34:59 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-26 01:34:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-26 01:34:59 (8458) [INFO] Trying other mirror.
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-26 01:34:59 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-26 01:34:59 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-26 01:34:59 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-26 01:34:59 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-26 01:34:59 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-26 01:34:59 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-26 01:34:59 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-26 01:34:59 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-26 01:34:59 (8458) [INFO]         or
* 2024-11-26 01:34:59 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-26 01:34:59 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-26 01:34:59 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-26 01:34:59 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-26 01:34:59 (8458) [INFO]         compromise:
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-26 01:34:59 (8458) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-26 01:34:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-26 01:34:59 (8475) [INFO] 
* 2024-11-26 01:34:59 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-26 01:34:59 (5520) [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-11-26 01:34:59 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-26 01:35:00 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-26 01:35:01 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Eh8FihIZeG/ea_profile.json
* 2024-11-26 01:35:09 (475) [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/Eh8FihIZeG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-26 01:35:09 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-28 01:33:31 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-28 01:33:31 (9517) [INFO] Script is up to date.
* 2024-11-28 01:33:32 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-28 01:33:32 (5935) [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-11-28 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-28 01:33:32 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-28 01:33:32 (8445) [INFO] 
* 2024-11-28 01:33:36 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-28 01:33:36 (3717) [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.

* 2024-11-28 01:33:36 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-28 01:33:36 (8445) [INFO] 
* 2024-11-28 01:33:50 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-28 01:33:50 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-28 01:33:50 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-28 01:33:50 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-28 01:33:50 (8458) [INFO] error    : Corrupt
* 2024-11-28 01:33:50 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-28 01:33:50 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-28 01:33:50 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-28 01:33:50 (8458) [INFO] error    : Corrupt
* 2024-11-28 01:33:50 (8458) [INFO] motopart_production.payment_status
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-28 01:33:50 (8458) [INFO] motopart_production.users
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-28 01:33:50 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-28 01:33:50 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 01:33:50 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-28 01:33:50 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 01:33:50 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-28 01:33:50 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 01:33:50 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-28 01:33:50 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 01:33:50 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-28 01:33:50 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 01:33:50 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-28 01:33:50 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 01:33:50 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-28 01:33:50 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-28 01:33:50 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-28 01:33:50 (8458) [INFO] error    : Corrupt
* 2024-11-28 01:33:50 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-28 01:33:50 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-28 01:33:50 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-28 01:33:50 (8458) [INFO] error    : Corrupt
* 2024-11-28 01:33:50 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-28 01:33:50 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-28 01:33:50 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-28 01:33:50 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-28 01:33:50 (8458) [INFO] error    : Corrupt
* 2024-11-28 01:33:50 (8475) [INFO] 
* 2024-11-28 01:33:50 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-28 01:33:50 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-28 01:33:50 (8445) [INFO] 
* 2024-11-28 01:33:55 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-28 01:33:55 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-28 01:33:55 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-28 01:33:55 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-28 01:33:55 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-28 01:33:55 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-28 01:33:55 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-28 01:33:55 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-28 01:33:55 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-28 01:33:55 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-28 01:33:55 (8445) [INFO] 
* 2024-11-28 01:33:55 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 01:33:55 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-28 01:33:57 (8458) [INFO]  * EA4: 63.247.64.58
* 2024-11-28 01:33:57 (8458) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-28 01:33:57 (8458) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-28 01:33:57 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-28 01:33:57 (8458) [INFO]  * remi-php72: mirror.team-cymru.com
* 2024-11-28 01:33:57 (8458) [INFO]  * remi-php73: mirror.team-cymru.com
* 2024-11-28 01:33:57 (8458) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-11-28 01:33:59 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-28 01:33:59 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-28 01:33:59 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-28 01:33:59 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-28 01:33:59 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-28 01:33:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-28 01:33:59 (8458) [INFO] Trying other mirror.
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-28 01:33:59 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 01:33:59 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 01:33:59 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-28 01:33:59 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-28 01:33:59 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-28 01:33:59 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 01:33:59 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-28 01:33:59 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-28 01:33:59 (8458) [INFO]         or
* 2024-11-28 01:33:59 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 01:33:59 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 01:33:59 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 01:33:59 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 01:33:59 (8458) [INFO]         compromise:
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-28 01:33:59 (8458) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-28 01:33:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-28 01:33:59 (8475) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-28 01:33:59 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-28 01:33:59 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-28 01:33:59 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-28 01:33:59 (8445) [INFO] 
* 2024-11-28 01:33:59 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 01:34:00 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-28 01:34:00 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-28 01:34:00 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-28 01:34:00 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-28 01:34:00 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-28 01:34:00 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-28 01:34:00 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-28 01:34:00 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-28 01:34:00 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-28 01:34:00 (8458) [INFO]               : yarn
* 2024-11-28 01:34:00 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-28 01:34:00 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-28 01:34:00 (8475) [INFO] 
* 2024-11-28 01:34:00 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-28 01:34:00 (8445) [INFO] 
* 2024-11-28 01:34:00 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 01:34:00 (8458) [INFO] Determining fastest mirrors
* 2024-11-28 01:34:05 (8458) [INFO]  * EA4: 63.247.64.58
* 2024-11-28 01:34:05 (8458) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-28 01:34:05 (8458) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-28 01:34:05 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-28 01:34:05 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-28 01:34:05 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-28 01:34:05 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-28 01:34:07 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-28 01:34:07 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-28 01:34:07 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-28 01:34:07 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-28 01:34:07 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-28 01:34:07 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-28 01:34:07 (8458) [INFO] Trying other mirror.
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-28 01:34:07 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 01:34:07 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 01:34:07 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-28 01:34:07 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-28 01:34:07 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-28 01:34:07 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 01:34:07 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-28 01:34:07 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-28 01:34:07 (8458) [INFO]         or
* 2024-11-28 01:34:07 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 01:34:07 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 01:34:07 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 01:34:07 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 01:34:07 (8458) [INFO]         compromise:
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-28 01:34:07 (8458) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-28 01:34:07 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-28 01:34:07 (8475) [INFO] 
* 2024-11-28 01:34:07 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-28 01:34:07 (5520) [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-11-28 01:34:07 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-28 01:34:07 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-28 01:34:08 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1nFSTZGupd/ea_profile.json
* 2024-11-28 01:34:12 (475) [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/1nFSTZGupd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-28 01:34:12 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-29 01:33:32 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-29 01:33:32 (9517) [INFO] Script is up to date.
* 2024-11-29 01:33:33 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-29 01:33:33 (5935) [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-11-29 01:33:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-29 01:33:33 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-29 01:33:33 (8445) [INFO] 
* 2024-11-29 01:33:41 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-29 01:33:41 (3717) [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.

* 2024-11-29 01:33:41 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-29 01:33:41 (8445) [INFO] 
* 2024-11-29 01:34:00 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-29 01:34:00 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-29 01:34:00 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-29 01:34:00 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-29 01:34:00 (8458) [INFO] error    : Corrupt
* 2024-11-29 01:34:00 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-29 01:34:00 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-29 01:34:00 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-29 01:34:00 (8458) [INFO] error    : Corrupt
* 2024-11-29 01:34:00 (8458) [INFO] motopart_production.payment_status
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-29 01:34:00 (8458) [INFO] motopart_production.users
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-29 01:34:00 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-29 01:34:00 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 01:34:00 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-29 01:34:00 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 01:34:00 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-29 01:34:00 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 01:34:00 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-29 01:34:00 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 01:34:00 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-29 01:34:00 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 01:34:00 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-29 01:34:00 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 01:34:00 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-29 01:34:00 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-29 01:34:00 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-29 01:34:00 (8458) [INFO] error    : Corrupt
* 2024-11-29 01:34:00 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-29 01:34:00 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-29 01:34:00 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-29 01:34:00 (8458) [INFO] error    : Corrupt
* 2024-11-29 01:34:00 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-29 01:34:00 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-29 01:34:00 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-29 01:34:00 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-29 01:34:00 (8458) [INFO] error    : Corrupt
* 2024-11-29 01:34:00 (8475) [INFO] 
* 2024-11-29 01:34:00 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-29 01:34:00 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-29 01:34:00 (8445) [INFO] 
* 2024-11-29 01:34:06 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-29 01:34:06 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-29 01:34:06 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-29 01:34:06 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-29 01:34:06 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-29 01:34:06 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-29 01:34:06 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-29 01:34:06 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-29 01:34:06 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-29 01:34:06 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-29 01:34:06 (8445) [INFO] 
* 2024-11-29 01:34:07 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 01:34:07 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-29 01:34:08 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-29 01:34:08 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-29 01:34:08 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-29 01:34:08 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-29 01:34:08 (8458) [INFO]  * remi-php72: rpms.remirepo.net
* 2024-11-29 01:34:08 (8458) [INFO]  * remi-php73: rpms.remirepo.net
* 2024-11-29 01:34:08 (8458) [INFO]  * remi-safe: rpms.remirepo.net
* 2024-11-29 01:34:10 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-29 01:34:10 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-29 01:34:10 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-29 01:34:10 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-29 01:34:10 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-29 01:34:10 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-29 01:34:10 (8458) [INFO] Trying other mirror.
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-29 01:34:10 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 01:34:10 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 01:34:10 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-29 01:34:10 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-29 01:34:10 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-29 01:34:10 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 01:34:10 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-29 01:34:10 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-29 01:34:10 (8458) [INFO]         or
* 2024-11-29 01:34:10 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 01:34:10 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 01:34:10 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 01:34:10 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 01:34:10 (8458) [INFO]         compromise:
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-29 01:34:10 (8458) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-29 01:34:10 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-29 01:34:10 (8475) [INFO] 
* 2024-11-29 01:34:10 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-29 01:34:10 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-29 01:34:10 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-29 01:34:10 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-29 01:34:10 (8445) [INFO] 
* 2024-11-29 01:34:11 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 01:34:11 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-29 01:34:11 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-29 01:34:11 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-29 01:34:11 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-29 01:34:11 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-29 01:34:11 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-29 01:34:11 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-29 01:34:11 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-29 01:34:11 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-29 01:34:11 (8458) [INFO]               : yarn
* 2024-11-29 01:34:11 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-29 01:34:11 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-29 01:34:11 (8475) [INFO] 
* 2024-11-29 01:34:11 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-29 01:34:11 (8445) [INFO] 
* 2024-11-29 01:34:11 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 01:34:11 (8458) [INFO] Determining fastest mirrors
* 2024-11-29 01:34:16 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-29 01:34:16 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-29 01:34:16 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-29 01:34:16 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-29 01:34:16 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-29 01:34:16 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-29 01:34:16 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-29 01:34:18 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-29 01:34:19 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-29 01:34:19 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-29 01:34:19 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-29 01:34:19 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-29 01:34:19 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-29 01:34:19 (8458) [INFO] Trying other mirror.
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-29 01:34:19 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 01:34:19 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 01:34:19 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-29 01:34:19 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-29 01:34:19 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-29 01:34:19 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 01:34:19 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-29 01:34:19 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-29 01:34:19 (8458) [INFO]         or
* 2024-11-29 01:34:19 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 01:34:19 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 01:34:19 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 01:34:19 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 01:34:19 (8458) [INFO]         compromise:
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-29 01:34:19 (8458) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-29 01:34:19 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-29 01:34:19 (8475) [INFO] 
* 2024-11-29 01:34:19 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-29 01:34:19 (5520) [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-11-29 01:34:19 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-29 01:34:19 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-29 01:34:20 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y3VOpYWBNI/ea_profile.json
* 2024-11-29 01:34:24 (475) [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/Y3VOpYWBNI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-29 01:34:24 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-30 01:36:13 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-30 01:36:13 (9517) [INFO] Script is up to date.
* 2024-11-30 01:36:14 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-11-30 01:36:14 (5935) [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-11-30 01:36:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-11-30 01:36:14 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-30 01:36:14 (8445) [INFO] 
* 2024-11-30 01:36:22 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-11-30 01:36:22 (3717) [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.

* 2024-11-30 01:36:22 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-30 01:36:22 (8445) [INFO] 
* 2024-11-30 01:36:33 (8458) [INFO] motopart_oc2.oc_address
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-30 01:36:33 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-11-30 01:36:33 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-11-30 01:36:33 (8458) [INFO] error    : Found 817 keys of 816
* 2024-11-30 01:36:33 (8458) [INFO] error    : Corrupt
* 2024-11-30 01:36:33 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-30 01:36:33 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-30 01:36:33 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-11-30 01:36:33 (8458) [INFO] error    : Corrupt
* 2024-11-30 01:36:33 (8458) [INFO] motopart_production.payment_status
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-30 01:36:33 (8458) [INFO] motopart_production.users
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-11-30 01:36:33 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-11-30 01:36:33 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 01:36:33 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-30 01:36:33 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 01:36:33 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-11-30 01:36:33 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 01:36:33 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-11-30 01:36:33 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 01:36:33 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-11-30 01:36:33 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 01:36:33 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-11-30 01:36:33 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 01:36:33 (8458) [INFO] optisoft_blog.wp_comments
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-30 01:36:33 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-11-30 01:36:33 (8458) [INFO] error    : Found 158 keys of 157
* 2024-11-30 01:36:33 (8458) [INFO] error    : Corrupt
* 2024-11-30 01:36:33 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-30 01:36:33 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-30 01:36:33 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-11-30 01:36:33 (8458) [INFO] error    : Corrupt
* 2024-11-30 01:36:33 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-11-30 01:36:33 (8458) [INFO] warning  : Table is marked as crashed
* 2024-11-30 01:36:33 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-11-30 01:36:33 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-11-30 01:36:33 (8458) [INFO] error    : Corrupt
* 2024-11-30 01:36:33 (8475) [INFO] 
* 2024-11-30 01:36:33 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-11-30 01:36:33 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-30 01:36:33 (8445) [INFO] 
* 2024-11-30 01:37:03 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-11-30 01:37:03 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-11-30 01:37:03 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-11-30 01:37:03 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-30 01:37:03 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-11-30 01:37:03 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-11-30 01:37:03 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-11-30 01:37:03 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-11-30 01:37:03 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-11-30 01:37:03 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-30 01:37:03 (8445) [INFO] 
* 2024-11-30 01:37:03 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 01:37:03 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-30 01:37:04 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-11-30 01:37:04 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-11-30 01:37:04 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-11-30 01:37:04 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-30 01:37:04 (8458) [INFO]  * remi-php72: rpms.remirepo.net
* 2024-11-30 01:37:04 (8458) [INFO]  * remi-php73: rpms.remirepo.net
* 2024-11-30 01:37:04 (8458) [INFO]  * remi-safe: rpms.remirepo.net
* 2024-11-30 01:37:10 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-30 01:37:11 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-30 01:37:11 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-30 01:37:11 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-30 01:37:11 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-30 01:37:11 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-30 01:37:11 (8458) [INFO] Trying other mirror.
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-30 01:37:11 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 01:37:11 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 01:37:11 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-30 01:37:11 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-30 01:37:11 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-30 01:37:11 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 01:37:11 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-30 01:37:11 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-30 01:37:11 (8458) [INFO]         or
* 2024-11-30 01:37:11 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 01:37:11 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 01:37:11 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 01:37:11 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 01:37:11 (8458) [INFO]         compromise:
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-30 01:37:11 (8458) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-30 01:37:11 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-30 01:37:11 (8475) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-30 01:37:11 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-30 01:37:11 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-30 01:37:11 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-30 01:37:11 (8445) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 01:37:11 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-11-30 01:37:11 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-30 01:37:11 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-30 01:37:11 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-11-30 01:37:11 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-30 01:37:11 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-11-30 01:37:11 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-11-30 01:37:11 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-11-30 01:37:11 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-30 01:37:11 (8458) [INFO]               : yarn
* 2024-11-30 01:37:11 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-30 01:37:11 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-11-30 01:37:11 (8475) [INFO] 
* 2024-11-30 01:37:11 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-30 01:37:11 (8445) [INFO] 
* 2024-11-30 01:37:11 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 01:37:11 (8458) [INFO] Determining fastest mirrors
* 2024-11-30 01:37:20 (8458) [INFO]  * EA4: 63.247.64.58
* 2024-11-30 01:37:20 (8458) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-11-30 01:37:20 (8458) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-11-30 01:37:20 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-11-30 01:37:20 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-11-30 01:37:20 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-11-30 01:37:20 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-11-30 01:37:25 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-30 01:37:25 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-11-30 01:37:25 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-11-30 01:37:25 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-11-30 01:37:25 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-11-30 01:37:25 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-30 01:37:25 (8458) [INFO] Trying other mirror.
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-11-30 01:37:25 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 01:37:25 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 01:37:25 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-30 01:37:25 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-30 01:37:25 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-30 01:37:25 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 01:37:25 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-30 01:37:25 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-11-30 01:37:25 (8458) [INFO]         or
* 2024-11-30 01:37:25 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 01:37:25 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 01:37:25 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 01:37:25 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 01:37:25 (8458) [INFO]         compromise:
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-11-30 01:37:25 (8458) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-11-30 01:37:25 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-30 01:37:25 (8475) [INFO] 
* 2024-11-30 01:37:25 (8458) [INFO] Is this ok [y/N]: 
* 2024-11-30 01:37:25 (5520) [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-11-30 01:37:25 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-11-30 01:37:25 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-30 01:37:26 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qMprMt6uyP/ea_profile.json
* 2024-11-30 01:37:31 (475) [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/qMprMt6uyP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-30 01:37:31 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-01 01:34:05 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-01 01:34:05 (9517) [INFO] Script is up to date.
* 2024-12-01 01:34:06 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-01 01:34:06 (5935) [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-12-01 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-01 01:34:08 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-01 01:34:08 (8445) [INFO] 
* 2024-12-01 01:34:13 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-01 01:34:13 (3717) [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.

* 2024-12-01 01:34:13 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-01 01:34:13 (8445) [INFO] 
* 2024-12-01 01:34:26 (8458) [INFO] motopart_oc2.oc_address
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-01 01:34:26 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-12-01 01:34:26 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-12-01 01:34:26 (8458) [INFO] error    : Found 817 keys of 816
* 2024-12-01 01:34:26 (8458) [INFO] error    : Corrupt
* 2024-12-01 01:34:26 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-01 01:34:26 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-12-01 01:34:26 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-12-01 01:34:26 (8458) [INFO] error    : Corrupt
* 2024-12-01 01:34:26 (8458) [INFO] motopart_production.payment_status
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-12-01 01:34:26 (8458) [INFO] motopart_production.users
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-12-01 01:34:26 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-12-01 01:34:26 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 01:34:26 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-12-01 01:34:26 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 01:34:26 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-12-01 01:34:26 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 01:34:26 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-12-01 01:34:26 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 01:34:26 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-12-01 01:34:26 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 01:34:26 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-12-01 01:34:26 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 01:34:26 (8458) [INFO] optisoft_blog.wp_comments
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-01 01:34:26 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-12-01 01:34:26 (8458) [INFO] error    : Found 158 keys of 157
* 2024-12-01 01:34:26 (8458) [INFO] error    : Corrupt
* 2024-12-01 01:34:26 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-01 01:34:26 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-12-01 01:34:26 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-12-01 01:34:26 (8458) [INFO] error    : Corrupt
* 2024-12-01 01:34:26 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-12-01 01:34:26 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-01 01:34:26 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-12-01 01:34:26 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-12-01 01:34:26 (8458) [INFO] error    : Corrupt
* 2024-12-01 01:34:26 (8475) [INFO] 
* 2024-12-01 01:34:26 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-12-01 01:34:26 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-01 01:34:26 (8445) [INFO] 
* 2024-12-01 01:34:31 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-01 01:34:31 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-01 01:34:31 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-01 01:34:31 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-01 01:34:31 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-01 01:34:31 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-01 01:34:31 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-01 01:34:31 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-01 01:34:31 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-01 01:34:31 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-01 01:34:31 (8445) [INFO] 
* 2024-12-01 01:34:31 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 01:34:31 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-01 01:34:32 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-01 01:34:32 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-01 01:34:32 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-01 01:34:32 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-01 01:34:32 (8458) [INFO]  * remi-php72: mirrors.upr.edu
* 2024-12-01 01:34:32 (8458) [INFO]  * remi-php73: mirrors.upr.edu
* 2024-12-01 01:34:32 (8458) [INFO]  * remi-safe: mirrors.upr.edu
* 2024-12-01 01:34:35 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-01 01:34:35 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-01 01:34:35 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-01 01:34:35 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-01 01:34:35 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-01 01:34:35 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-01 01:34:35 (8458) [INFO] Trying other mirror.
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-01 01:34:35 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 01:34:35 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 01:34:35 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-01 01:34:35 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-01 01:34:35 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-01 01:34:35 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 01:34:35 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-01 01:34:35 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-01 01:34:35 (8458) [INFO]         or
* 2024-12-01 01:34:35 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 01:34:35 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 01:34:35 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 01:34:35 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 01:34:35 (8458) [INFO]         compromise:
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-01 01:34:35 (8458) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-01 01:34:35 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-01 01:34:35 (8475) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO] Is this ok [y/N]: 
* 2024-12-01 01:34:35 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-01 01:34:35 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-01 01:34:35 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-01 01:34:35 (8445) [INFO] 
* 2024-12-01 01:34:35 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 01:34:36 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-01 01:34:36 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-01 01:34:36 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-01 01:34:36 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-01 01:34:36 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-01 01:34:36 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-01 01:34:36 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-01 01:34:36 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-01 01:34:36 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-01 01:34:36 (8458) [INFO]               : yarn
* 2024-12-01 01:34:36 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-01 01:34:36 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-01 01:34:36 (8475) [INFO] 
* 2024-12-01 01:34:36 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-01 01:34:36 (8445) [INFO] 
* 2024-12-01 01:34:36 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 01:34:36 (8458) [INFO] Determining fastest mirrors
* 2024-12-01 01:34:39 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-01 01:34:39 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-01 01:34:39 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-01 01:34:39 (8458) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-01 01:34:39 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-01 01:34:39 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-01 01:34:39 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-01 01:34:42 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-01 01:34:42 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-01 01:34:42 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-01 01:34:42 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-01 01:34:42 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-01 01:34:42 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-01 01:34:42 (8458) [INFO] Trying other mirror.
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-01 01:34:42 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 01:34:42 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 01:34:42 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-01 01:34:42 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-01 01:34:42 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-01 01:34:42 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 01:34:42 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-01 01:34:42 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-01 01:34:42 (8458) [INFO]         or
* 2024-12-01 01:34:42 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 01:34:42 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 01:34:42 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 01:34:42 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 01:34:42 (8458) [INFO]         compromise:
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-01 01:34:42 (8458) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-01 01:34:42 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-01 01:34:42 (8475) [INFO] 
* 2024-12-01 01:34:42 (8458) [INFO] Is this ok [y/N]: 
* 2024-12-01 01:34:42 (5520) [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-12-01 01:34:42 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-01 01:34:42 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-01 01:34:44 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p2u0NUsLLx/ea_profile.json
* 2024-12-01 01:34:49 (475) [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/p2u0NUsLLx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-01 01:34:49 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-03 01:33:24 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-03 01:33:24 (9517) [INFO] Script is up to date.
* 2024-12-03 01:33:25 (249) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-03 01:33:25 (5935) [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-12-03 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-03 01:33:25 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-03 01:33:25 (8445) [INFO] 
* 2024-12-03 01:33:29 (3710) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-03 01:33:29 (3717) [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.

* 2024-12-03 01:33:29 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-03 01:33:29 (8445) [INFO] 
* 2024-12-03 01:33:46 (8458) [INFO] motopart_oc2.oc_address
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-03 01:33:46 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Size of indexfile is: 20480      Should be: 19456
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Size of datafile is: 76964       Should be: 76872
* 2024-12-03 01:33:46 (8458) [INFO] error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
* 2024-12-03 01:33:46 (8458) [INFO] error    : Found 817 keys of 816
* 2024-12-03 01:33:46 (8458) [INFO] error    : Corrupt
* 2024-12-03 01:33:46 (8458) [INFO] motopart_oc2.oc_customer_login
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-03 01:33:46 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-12-03 01:33:46 (8458) [INFO] error    : Size of datafile is: 28672         Should be: 28692
* 2024-12-03 01:33:46 (8458) [INFO] error    : Corrupt
* 2024-12-03 01:33:46 (8458) [INFO] motopart_production.payment_status
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-12-03 01:33:46 (8458) [INFO] motopart_production.users
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Found row where the auto_increment column has the value 0
* 2024-12-03 01:33:46 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens
* 2024-12-03 01:33:46 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 01:33:46 (8458) [INFO] ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-12-03 01:33:46 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 01:33:46 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens
* 2024-12-03 01:33:46 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 01:33:46 (8458) [INFO] ncfnigeria_dev2017.cth_finder_tokens_aggregate
* 2024-12-03 01:33:46 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 01:33:46 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
* 2024-12-03 01:33:46 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 01:33:46 (8458) [INFO] ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
* 2024-12-03 01:33:46 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 01:33:46 (8458) [INFO] optisoft_blog.wp_comments
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-03 01:33:46 (8458) [INFO] warning  : 1 client is using or hasn't closed the table properly
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Size of datafile is: 73108       Should be: 72752
* 2024-12-03 01:33:46 (8458) [INFO] error    : Found 158 keys of 157
* 2024-12-03 01:33:46 (8458) [INFO] error    : Corrupt
* 2024-12-03 01:33:46 (8458) [INFO] qui10000_lhlp1.livehelp_users
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-03 01:33:46 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-12-03 01:33:46 (8458) [INFO] error    : Size of datafile is: 49917952         Should be: 49918092
* 2024-12-03 01:33:46 (8458) [INFO] error    : Corrupt
* 2024-12-03 01:33:46 (8458) [INFO] qui10000_lhlp1.livehelp_visit_track
* 2024-12-03 01:33:46 (8458) [INFO] warning  : Table is marked as crashed
* 2024-12-03 01:33:46 (8458) [INFO] warning  : 2 clients are using or haven't closed the table properly
* 2024-12-03 01:33:46 (8458) [INFO] error    : Size of datafile is: 36311040         Should be: 36311084
* 2024-12-03 01:33:46 (8458) [INFO] error    : Corrupt
* 2024-12-03 01:33:46 (8475) [INFO] 
* 2024-12-03 01:33:46 (249) [WARN] *** Elevation Blocker detected: ***
We have found the following problems with your database(s):
motopart_oc2.oc_address
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of indexfile is: 20480      Should be: 19456
warning  : Size of datafile is: 76964       Should be: 76872
error    : Invalid key block position: 19456  key block size: 1024  file_length: 19456
error    : Found 817 keys of 816
error    : Corrupt
motopart_oc2.oc_customer_login
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
error    : Size of datafile is: 28672         Should be: 28692
error    : Corrupt
motopart_production.payment_status
warning  : Found row where the auto_increment column has the value 0
motopart_production.users
warning  : Found row where the auto_increment column has the value 0
ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_dev2017.cth_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens
note     : The storage engine for the table doesn't support check
ncfnigeria_ncfniger_reloaded.fcont_finder_tokens_aggregate
note     : The storage engine for the table doesn't support check
optisoft_blog.wp_comments
warning  : Table is marked as crashed
warning  : 1 client is using or hasn't closed the table properly
warning  : Size of datafile is: 73108       Should be: 72752
error    : Found 158 keys of 157
error    : Corrupt
qui10000_lhlp1.livehelp_users
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 49917952         Should be: 49918092
error    : Corrupt
qui10000_lhlp1.livehelp_visit_track
warning  : Table is marked as crashed
warning  : 2 clients are using or haven't closed the table properly
error    : Size of datafile is: 36311040         Should be: 36311084
error    : Corrupt
You should repair any corrupted databases before elevating the system.

* 2024-12-03 01:33:46 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-03 01:33:46 (8445) [INFO] 
* 2024-12-03 01:33:51 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-03 01:33:51 (5651) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-03 01:33:51 (5651) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-03 01:33:51 (5627) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-03 01:33:51 (5627) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-03 01:33:51 (5651) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-03 01:33:51 (5651) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-03 01:33:51 (5627) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-03 01:33:51 (5651) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-03 01:33:51 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-03 01:33:51 (8445) [INFO] 
* 2024-12-03 01:33:51 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 01:33:51 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-03 01:33:53 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-03 01:33:53 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-03 01:33:53 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-03 01:33:53 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-03 01:33:53 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-03 01:33:53 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-03 01:33:53 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-03 01:33:54 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-03 01:33:54 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-03 01:33:54 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-03 01:33:54 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-03 01:33:54 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-03 01:33:54 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-03 01:33:54 (8458) [INFO] Trying other mirror.
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-03 01:33:54 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 01:33:54 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 01:33:54 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-03 01:33:54 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-03 01:33:54 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-03 01:33:54 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 01:33:54 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-03 01:33:54 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-03 01:33:54 (8458) [INFO]         or
* 2024-12-03 01:33:54 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 01:33:54 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 01:33:54 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 01:33:54 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 01:33:54 (8458) [INFO]         compromise:
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-03 01:33:54 (8458) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-03 01:33:54 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-03 01:33:54 (8475) [INFO] 
* 2024-12-03 01:33:54 (8458) [INFO] Is this ok [y/N]: 
* 2024-12-03 01:33:54 (5510) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-03 01:33:54 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-03 01:33:54 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-03 01:33:54 (8445) [INFO] 
* 2024-12-03 01:33:55 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 01:33:55 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-03 01:33:55 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-03 01:33:55 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-03 01:33:55 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-03 01:33:55 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-03 01:33:55 (8458) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-03 01:33:55 (8458) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-03 01:33:55 (8458) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-03 01:33:55 (8458) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-03 01:33:55 (8458) [INFO]               : yarn
* 2024-12-03 01:33:55 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-03 01:33:55 (8458) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-03 01:33:55 (8475) [INFO] 
* 2024-12-03 01:33:55 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-03 01:33:55 (8445) [INFO] 
* 2024-12-03 01:33:55 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 01:33:55 (8458) [INFO] Determining fastest mirrors
* 2024-12-03 01:33:58 (8458) [INFO]  * EA4: 185.125.185.32
* 2024-12-03 01:33:58 (8458) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-03 01:33:58 (8458) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-03 01:33:58 (8458) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-03 01:33:58 (8458) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-03 01:33:58 (8458) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-03 01:33:58 (8458) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-03 01:33:59 (8458) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-03 01:33:59 (8458) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-03 01:33:59 (8458) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-03 01:33:59 (8458) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-03 01:33:59 (8458) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-03 01:33:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-03 01:33:59 (8458) [INFO] Trying other mirror.
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-03 01:33:59 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 01:33:59 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 01:33:59 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-03 01:33:59 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-03 01:33:59 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-03 01:33:59 (8458) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 01:33:59 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-03 01:33:59 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-03 01:33:59 (8458) [INFO]         or
* 2024-12-03 01:33:59 (8458) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 01:33:59 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 01:33:59 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 01:33:59 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 01:33:59 (8458) [INFO]         compromise:
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-03 01:33:59 (8458) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-03 01:33:59 (8458) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-03 01:33:59 (8475) [INFO] 
* 2024-12-03 01:33:59 (8458) [INFO] Is this ok [y/N]: 
* 2024-12-03 01:33:59 (5520) [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-12-03 01:33:59 (5521) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-03 01:33:59 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-03 01:34:01 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8qxuJ5Iial/ea_profile.json
* 2024-12-03 01:34:04 (475) [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/8qxuJ5Iial/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-03 01:34:04 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-04 01:33:30 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-04 01:33:30 (9500) [INFO] Newer version of script found. Downloading.
* 2024-12-04 01:33:31 (9509) [INFO] Script update to version 59 successful.
* 2024-12-04 01:33:32 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-04 01:33:32 (6225) [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-12-04 01:33:32 (252) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2024-12-04 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-04 01:33:32 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-04 01:33:32 (9238) [INFO] 
* 2024-12-04 01:33:37 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-04 01:33:37 (3970) [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.

* 2024-12-04 01:33:37 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-04 01:33:37 (9238) [INFO] 
* 2024-12-04 01:33:53 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-04 01:33:53 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-04 01:33:53 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-04 01:33:53 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-04 01:33:53 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-04 01:33:53 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-04 01:33:53 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-04 01:33:53 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-04 01:33:53 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-04 01:33:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-04 01:33:53 (9238) [INFO] 
* 2024-12-04 01:33:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 01:33:53 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-04 01:33:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-04 01:33:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-04 01:33:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-04 01:33:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-04 01:33:54 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-04 01:33:54 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-04 01:33:54 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-04 01:33:59 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-04 01:33:59 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-04 01:33:59 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-04 01:33:59 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-04 01:33:59 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-04 01:33:59 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-04 01:33:59 (9251) [INFO] Trying other mirror.
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-04 01:33:59 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 01:33:59 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 01:33:59 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-04 01:33:59 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-04 01:33:59 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-04 01:33:59 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 01:33:59 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-04 01:33:59 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-04 01:33:59 (9251) [INFO]         or
* 2024-12-04 01:33:59 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 01:33:59 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 01:33:59 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 01:33:59 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 01:33:59 (9251) [INFO]         compromise:
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-04 01:33:59 (9251) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-04 01:33:59 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-04 01:33:59 (9268) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-04 01:33:59 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-04 01:33:59 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-04 01:33:59 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-04 01:33:59 (9238) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 01:33:59 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-04 01:33:59 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-04 01:33:59 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-04 01:33:59 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-04 01:33:59 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-04 01:33:59 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-04 01:33:59 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-04 01:33:59 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-04 01:33:59 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-04 01:33:59 (9251) [INFO]               : yarn
* 2024-12-04 01:33:59 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-04 01:33:59 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-04 01:33:59 (9268) [INFO] 
* 2024-12-04 01:33:59 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-04 01:33:59 (9238) [INFO] 
* 2024-12-04 01:33:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 01:34:00 (9251) [INFO] Determining fastest mirrors
* 2024-12-04 01:34:04 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-04 01:34:04 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-04 01:34:04 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-04 01:34:04 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-04 01:34:04 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-04 01:34:04 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-04 01:34:04 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-04 01:34:05 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-04 01:34:05 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-04 01:34:05 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-04 01:34:05 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-04 01:34:05 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-04 01:34:05 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-04 01:34:05 (9251) [INFO] Trying other mirror.
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-04 01:34:05 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 01:34:05 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 01:34:05 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-04 01:34:05 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-04 01:34:05 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-04 01:34:05 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 01:34:05 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-04 01:34:05 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-04 01:34:05 (9251) [INFO]         or
* 2024-12-04 01:34:05 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 01:34:05 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 01:34:05 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 01:34:05 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 01:34:05 (9251) [INFO]         compromise:
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-04 01:34:05 (9251) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-04 01:34:05 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-04 01:34:05 (9268) [INFO] 
* 2024-12-04 01:34:05 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-04 01:34:05 (5803) [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-12-04 01:34:05 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-04 01:34:05 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-04 01:34:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3becyx0aNY/ea_profile.json
* 2024-12-04 01:34:10 (484) [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/3becyx0aNY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-04 01:34:10 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-05 01:33:26 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-05 01:33:26 (10313) [INFO] Script is up to date.
* 2024-12-05 01:33:28 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-05 01:33:28 (6225) [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-12-05 01:33:28 (252) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2024-12-05 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-05 01:33:28 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-05 01:33:28 (9238) [INFO] 
* 2024-12-05 01:33:32 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-05 01:33:32 (3970) [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.

* 2024-12-05 01:33:32 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-05 01:33:32 (9238) [INFO] 
* 2024-12-05 01:33:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-05 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-05 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-05 01:33:47 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-05 01:33:47 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-05 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-05 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-05 01:33:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-05 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-05 01:33:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-05 01:33:47 (9238) [INFO] 
* 2024-12-05 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 01:33:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-05 01:33:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-05 01:33:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-05 01:33:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-05 01:33:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-05 01:33:48 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-05 01:33:48 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-05 01:33:48 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-05 01:33:51 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-05 01:33:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-05 01:33:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-05 01:33:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-05 01:33:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-05 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-05 01:33:51 (9251) [INFO] Trying other mirror.
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-05 01:33:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-05 01:33:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-05 01:33:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-05 01:33:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-05 01:33:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-05 01:33:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-05 01:33:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-05 01:33:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-05 01:33:51 (9251) [INFO]         or
* 2024-12-05 01:33:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-05 01:33:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-05 01:33:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-05 01:33:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-05 01:33:51 (9251) [INFO]         compromise:
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-05 01:33:51 (9251) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-05 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-05 01:33:51 (9268) [INFO] 
* 2024-12-05 01:33:51 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-05 01:33:51 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-05 01:33:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-05 01:33:51 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-05 01:33:51 (9238) [INFO] 
* 2024-12-05 01:33:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 01:33:52 (9251) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 576384.
* 2024-12-05 01:33:52 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-05 01:33:52 (9251) [INFO]   The other application is: yum
* 2024-12-05 01:33:52 (9251) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-12-05 01:33:52 (9251) [INFO]     Started: Thu Dec  5 01:33:39 2024 - 00:13 ago
* 2024-12-05 01:33:52 (9251) [INFO]     State  : Sleeping, pid: 576384
* 2024-12-05 01:33:54 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-05 01:33:54 (9251) [INFO]   The other application is: yum
* 2024-12-05 01:33:54 (9251) [INFO]     Memory :  38 M RSS (333 MB VSZ)
* 2024-12-05 01:33:54 (9251) [INFO]     Started: Thu Dec  5 01:33:39 2024 - 00:15 ago
* 2024-12-05 01:33:54 (9251) [INFO]     State  : Sleeping, pid: 576384
* 2024-12-05 01:33:56 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-05 01:33:56 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-05 01:33:56 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-05 01:33:56 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-05 01:33:56 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-05 01:33:56 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-05 01:33:56 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-05 01:33:56 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-05 01:33:56 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-05 01:33:56 (9251) [INFO]               : yarn
* 2024-12-05 01:33:56 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-05 01:33:56 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-05 01:33:56 (9268) [INFO] 
* 2024-12-05 01:33:56 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-05 01:33:56 (9238) [INFO] 
* 2024-12-05 01:33:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 01:33:56 (9251) [INFO] Determining fastest mirrors
* 2024-12-05 01:34:01 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-05 01:34:01 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-05 01:34:01 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-05 01:34:01 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-05 01:34:01 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-05 01:34:01 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-05 01:34:01 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-05 01:34:04 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-05 01:34:04 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-05 01:34:04 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-05 01:34:04 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-05 01:34:04 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-05 01:34:04 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-05 01:34:04 (9251) [INFO] Trying other mirror.
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-05 01:34:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-05 01:34:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-05 01:34:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-05 01:34:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-05 01:34:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-05 01:34:04 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-05 01:34:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-05 01:34:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-05 01:34:04 (9251) [INFO]         or
* 2024-12-05 01:34:04 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-05 01:34:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-05 01:34:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-05 01:34:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-05 01:34:04 (9251) [INFO]         compromise:
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-05 01:34:04 (9251) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-05 01:34:04 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-05 01:34:04 (9268) [INFO] 
* 2024-12-05 01:34:04 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-05 01:34:04 (5803) [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-12-05 01:34:04 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-05 01:34:04 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-05 01:34:05 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VT8h_iOALT/ea_profile.json
* 2024-12-05 01:34:10 (484) [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/VT8h_iOALT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-05 01:34:10 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-06 01:33:33 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-06 01:33:33 (10313) [INFO] Script is up to date.
* 2024-12-06 01:33:34 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-06 01:33:34 (6225) [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-12-06 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-06 01:33:34 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-06 01:33:34 (9238) [INFO] 
* 2024-12-06 01:33:38 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-06 01:33:38 (3970) [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.

* 2024-12-06 01:33:38 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-06 01:33:38 (9238) [INFO] 
* 2024-12-06 01:34:00 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-06 01:34:00 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-06 01:34:00 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-06 01:34:00 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-06 01:34:00 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-06 01:34:00 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-06 01:34:00 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-06 01:34:00 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-06 01:34:00 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-06 01:34:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-06 01:34:00 (9238) [INFO] 
* 2024-12-06 01:34:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 01:34:00 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-06 01:34:02 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-06 01:34:02 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-06 01:34:02 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-06 01:34:02 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-06 01:34:02 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-06 01:34:02 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-06 01:34:02 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-06 01:34:05 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-06 01:34:05 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-06 01:34:05 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-06 01:34:05 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-06 01:34:05 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-06 01:34:05 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-06 01:34:05 (9251) [INFO] Trying other mirror.
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-06 01:34:05 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-06 01:34:05 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-06 01:34:05 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-06 01:34:05 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-06 01:34:05 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-06 01:34:05 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-06 01:34:05 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-06 01:34:05 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-06 01:34:05 (9251) [INFO]         or
* 2024-12-06 01:34:05 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-06 01:34:05 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-06 01:34:05 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-06 01:34:05 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-06 01:34:05 (9251) [INFO]         compromise:
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-06 01:34:05 (9251) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-06 01:34:05 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-06 01:34:05 (9268) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-06 01:34:05 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-06 01:34:05 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-06 01:34:05 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-06 01:34:05 (9238) [INFO] 
* 2024-12-06 01:34:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 01:34:05 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-06 01:34:05 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-06 01:34:05 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-06 01:34:05 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-06 01:34:05 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-06 01:34:05 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-06 01:34:05 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-06 01:34:05 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-06 01:34:05 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-06 01:34:05 (9251) [INFO]               : yarn
* 2024-12-06 01:34:06 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-06 01:34:06 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-06 01:34:06 (9268) [INFO] 
* 2024-12-06 01:34:06 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-06 01:34:06 (9238) [INFO] 
* 2024-12-06 01:34:06 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 01:34:06 (9251) [INFO] Determining fastest mirrors
* 2024-12-06 01:34:11 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-06 01:34:11 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-06 01:34:11 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-06 01:34:11 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-06 01:34:11 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-06 01:34:11 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-06 01:34:11 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-06 01:34:13 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-06 01:34:13 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-06 01:34:13 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-06 01:34:13 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-06 01:34:13 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-06 01:34:13 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-06 01:34:13 (9251) [INFO] Trying other mirror.
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-06 01:34:13 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-06 01:34:13 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-06 01:34:13 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-06 01:34:13 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-06 01:34:13 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-06 01:34:13 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-06 01:34:13 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-06 01:34:13 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-06 01:34:13 (9251) [INFO]         or
* 2024-12-06 01:34:13 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-06 01:34:13 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-06 01:34:13 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-06 01:34:13 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-06 01:34:13 (9251) [INFO]         compromise:
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-06 01:34:13 (9251) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-06 01:34:13 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-06 01:34:13 (9268) [INFO] 
* 2024-12-06 01:34:13 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-06 01:34:13 (5803) [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-12-06 01:34:13 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-06 01:34:13 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-06 01:34:15 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L2sd43YnmR/ea_profile.json
* 2024-12-06 01:34:19 (484) [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/L2sd43YnmR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-06 01:34:19 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-07 01:34:13 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-07 01:34:13 (10313) [INFO] Script is up to date.
* 2024-12-07 01:34:14 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-07 01:34:14 (6225) [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-12-07 01:34:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-07 01:34:14 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-07 01:34:14 (9238) [INFO] 
* 2024-12-07 01:34:19 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-07 01:34:19 (3970) [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.

* 2024-12-07 01:34:19 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-07 01:34:19 (9238) [INFO] 
* 2024-12-07 01:34:28 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-07 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-07 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-07 01:34:28 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-07 01:34:28 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-07 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-07 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-07 01:34:28 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-07 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-07 01:34:28 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-07 01:34:28 (9238) [INFO] 
* 2024-12-07 01:34:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 01:34:29 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-07 01:34:30 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-07 01:34:30 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-07 01:34:30 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-07 01:34:30 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-07 01:34:30 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-07 01:34:30 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-07 01:34:30 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-07 01:34:32 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-07 01:34:32 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-07 01:34:32 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-07 01:34:32 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-07 01:34:32 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-07 01:34:32 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-07 01:34:32 (9251) [INFO] Trying other mirror.
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-07 01:34:32 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-07 01:34:32 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-07 01:34:32 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-07 01:34:32 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-07 01:34:32 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-07 01:34:32 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-07 01:34:32 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-07 01:34:32 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-07 01:34:32 (9251) [INFO]         or
* 2024-12-07 01:34:32 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-07 01:34:32 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-07 01:34:32 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-07 01:34:32 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-07 01:34:32 (9251) [INFO]         compromise:
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-07 01:34:32 (9251) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-07 01:34:32 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-07 01:34:32 (9268) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-07 01:34:32 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-07 01:34:32 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-07 01:34:32 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-07 01:34:32 (9238) [INFO] 
* 2024-12-07 01:34:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 01:34:32 (9251) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 186105.
* 2024-12-07 01:34:32 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-07 01:34:32 (9251) [INFO]   The other application is: yum
* 2024-12-07 01:34:32 (9251) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-12-07 01:34:32 (9251) [INFO]     Started: Sat Dec  7 01:34:22 2024 - 00:10 ago
* 2024-12-07 01:34:32 (9251) [INFO]     State  : Sleeping, pid: 186105
* 2024-12-07 01:34:34 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-07 01:34:34 (9251) [INFO]   The other application is: yum
* 2024-12-07 01:34:34 (9251) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-12-07 01:34:34 (9251) [INFO]     Started: Sat Dec  7 01:34:22 2024 - 00:12 ago
* 2024-12-07 01:34:34 (9251) [INFO]     State  : Sleeping, pid: 186105
* 2024-12-07 01:34:36 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-07 01:34:36 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-07 01:34:36 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-07 01:34:36 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-07 01:34:36 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-07 01:34:36 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-07 01:34:36 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-07 01:34:36 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-07 01:34:36 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-07 01:34:36 (9251) [INFO]               : yarn
* 2024-12-07 01:34:36 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-07 01:34:36 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-07 01:34:36 (9268) [INFO] 
* 2024-12-07 01:34:36 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-07 01:34:36 (9238) [INFO] 
* 2024-12-07 01:34:36 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 01:34:37 (9251) [INFO] Determining fastest mirrors
* 2024-12-07 01:34:39 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-07 01:34:39 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-07 01:34:39 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-07 01:34:39 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-07 01:34:39 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-07 01:34:39 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-07 01:34:39 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-07 01:34:42 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-07 01:34:42 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-07 01:34:42 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-07 01:34:42 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-07 01:34:42 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-07 01:34:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-07 01:34:42 (9251) [INFO] Trying other mirror.
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-07 01:34:42 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-07 01:34:42 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-07 01:34:42 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-07 01:34:42 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-07 01:34:42 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-07 01:34:42 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-07 01:34:42 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-07 01:34:42 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-07 01:34:42 (9251) [INFO]         or
* 2024-12-07 01:34:42 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-07 01:34:42 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-07 01:34:42 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-07 01:34:42 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-07 01:34:42 (9251) [INFO]         compromise:
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-07 01:34:42 (9251) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-07 01:34:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-07 01:34:42 (9268) [INFO] 
* 2024-12-07 01:34:42 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-07 01:34:42 (5803) [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-12-07 01:34:42 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-07 01:34:42 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-07 01:34:43 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KUDe550E2_/ea_profile.json
* 2024-12-07 01:34:48 (484) [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/KUDe550E2_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-07 01:34:48 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-08 01:34:03 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-08 01:34:03 (10313) [INFO] Script is up to date.
* 2024-12-08 01:34:07 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-08 01:34:07 (6225) [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-12-08 01:34:09 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-08 01:34:09 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-08 01:34:09 (9238) [INFO] 
* 2024-12-08 01:34:13 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-08 01:34:13 (3970) [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.

* 2024-12-08 01:34:13 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-08 01:34:13 (9238) [INFO] 
* 2024-12-08 01:34:18 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-08 01:34:18 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-08 01:34:18 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-08 01:34:18 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-08 01:34:18 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-08 01:34:18 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-08 01:34:18 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-08 01:34:18 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-08 01:34:18 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-08 01:34:18 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-08 01:34:18 (9238) [INFO] 
* 2024-12-08 01:34:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 01:34:19 (9251) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 510270.
* 2024-12-08 01:34:19 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-08 01:34:19 (9251) [INFO]   The other application is: yum
* 2024-12-08 01:34:19 (9251) [INFO]     Memory :  37 M RSS (331 MB VSZ)
* 2024-12-08 01:34:19 (9251) [INFO]     Started: Sun Dec  8 01:34:13 2024 - 00:06 ago
* 2024-12-08 01:34:19 (9251) [INFO]     State  : Sleeping, pid: 510270
* 2024-12-08 01:34:21 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-08 01:34:21 (9251) [INFO]   The other application is: yum
* 2024-12-08 01:34:21 (9251) [INFO]     Memory :  39 M RSS (333 MB VSZ)
* 2024-12-08 01:34:21 (9251) [INFO]     Started: Sun Dec  8 01:34:13 2024 - 00:08 ago
* 2024-12-08 01:34:21 (9251) [INFO]     State  : Sleeping, pid: 510270
* 2024-12-08 01:34:23 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-08 01:34:23 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-08 01:34:23 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-08 01:34:23 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-08 01:34:23 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-08 01:34:23 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-08 01:34:23 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-08 01:34:23 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-08 01:34:27 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-08 01:34:27 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-08 01:34:27 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-08 01:34:27 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-08 01:34:27 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-08 01:34:27 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-08 01:34:27 (9251) [INFO] Trying other mirror.
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-08 01:34:27 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-08 01:34:27 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-08 01:34:27 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-08 01:34:27 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-08 01:34:27 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-08 01:34:27 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-08 01:34:27 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-08 01:34:27 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-08 01:34:27 (9251) [INFO]         or
* 2024-12-08 01:34:27 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-08 01:34:27 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-08 01:34:27 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-08 01:34:27 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-08 01:34:27 (9251) [INFO]         compromise:
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-08 01:34:27 (9251) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-08 01:34:27 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-08 01:34:27 (9268) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-08 01:34:27 (5793) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 510270.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  37 M RSS (331 MB VSZ)
    Started: Sun Dec  8 01:34:13 2024 - 00:06 ago
    State  : Sleeping, pid: 510270
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  39 M RSS (333 MB VSZ)
    Started: Sun Dec  8 01:34:13 2024 - 00:08 ago
    State  : Sleeping, pid: 510270
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-08 01:34:27 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-08 01:34:27 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-08 01:34:27 (9238) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 01:34:27 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-08 01:34:27 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-08 01:34:27 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-08 01:34:27 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-08 01:34:27 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-08 01:34:27 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-08 01:34:27 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-08 01:34:27 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-08 01:34:27 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-08 01:34:27 (9251) [INFO]               : yarn
* 2024-12-08 01:34:27 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-08 01:34:27 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-08 01:34:27 (9268) [INFO] 
* 2024-12-08 01:34:27 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-08 01:34:27 (9238) [INFO] 
* 2024-12-08 01:34:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 01:34:28 (9251) [INFO] Determining fastest mirrors
* 2024-12-08 01:34:31 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-08 01:34:31 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-08 01:34:31 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-08 01:34:31 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-08 01:34:31 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-08 01:34:31 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-08 01:34:31 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-08 01:34:34 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-08 01:34:35 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-08 01:34:35 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-08 01:34:35 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-08 01:34:35 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-08 01:34:35 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-08 01:34:35 (9251) [INFO] Trying other mirror.
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-08 01:34:35 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-08 01:34:35 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-08 01:34:35 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-08 01:34:35 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-08 01:34:35 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-08 01:34:35 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-08 01:34:35 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-08 01:34:35 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-08 01:34:35 (9251) [INFO]         or
* 2024-12-08 01:34:35 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-08 01:34:35 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-08 01:34:35 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-08 01:34:35 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-08 01:34:35 (9251) [INFO]         compromise:
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-08 01:34:35 (9251) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-08 01:34:35 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-08 01:34:35 (9268) [INFO] 
* 2024-12-08 01:34:35 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-08 01:34:35 (5803) [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-12-08 01:34:35 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-08 01:34:35 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-08 01:34:36 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/I7P4Rch3kR/ea_profile.json
* 2024-12-08 01:34:41 (484) [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/I7P4Rch3kR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-08 01:34:41 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-09 01:33:31 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-09 01:33:31 (10313) [INFO] Script is up to date.
* 2024-12-09 01:33:33 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-09 01:33:33 (6225) [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-12-09 01:33:33 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-09 01:33:33 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-09 01:33:33 (9238) [INFO] 
* 2024-12-09 01:33:38 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-09 01:33:38 (3970) [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.

* 2024-12-09 01:33:38 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-09 01:33:38 (9238) [INFO] 
* 2024-12-09 01:33:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-09 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-09 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-09 01:33:46 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-09 01:33:46 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-09 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-09 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-09 01:33:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-09 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-09 01:33:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-09 01:33:46 (9238) [INFO] 
* 2024-12-09 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 01:33:46 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-09 01:33:47 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-09 01:33:47 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-09 01:33:47 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-09 01:33:47 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-09 01:33:47 (9251) [INFO]  * remi-php72: mirror.team-cymru.com
* 2024-12-09 01:33:47 (9251) [INFO]  * remi-php73: mirror.team-cymru.com
* 2024-12-09 01:33:47 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2024-12-09 01:33:48 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-09 01:33:49 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-09 01:33:49 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-09 01:33:49 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-09 01:33:49 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-09 01:33:49 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-09 01:33:49 (9251) [INFO] Trying other mirror.
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-09 01:33:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 01:33:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 01:33:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-09 01:33:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-09 01:33:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-09 01:33:49 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 01:33:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-09 01:33:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-09 01:33:49 (9251) [INFO]         or
* 2024-12-09 01:33:49 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 01:33:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 01:33:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 01:33:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 01:33:49 (9251) [INFO]         compromise:
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-09 01:33:49 (9251) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-09 01:33:49 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-09 01:33:49 (9268) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-09 01:33:49 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-09 01:33:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-09 01:33:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-09 01:33:49 (9238) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 01:33:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-09 01:33:49 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-09 01:33:49 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-09 01:33:49 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-09 01:33:49 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-09 01:33:49 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-09 01:33:49 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-09 01:33:49 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-09 01:33:49 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-09 01:33:49 (9251) [INFO]               : yarn
* 2024-12-09 01:33:49 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-09 01:33:49 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-09 01:33:49 (9268) [INFO] 
* 2024-12-09 01:33:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-09 01:33:49 (9238) [INFO] 
* 2024-12-09 01:33:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 01:33:50 (9251) [INFO] Determining fastest mirrors
* 2024-12-09 01:33:54 (9251) [INFO]  * EA4: 63.247.64.58
* 2024-12-09 01:33:54 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-12-09 01:33:54 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-12-09 01:33:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-09 01:33:54 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-09 01:33:54 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-09 01:33:54 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-09 01:33:56 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-09 01:33:56 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-09 01:33:56 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-09 01:33:56 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-09 01:33:56 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-09 01:33:56 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-09 01:33:56 (9251) [INFO] Trying other mirror.
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-09 01:33:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 01:33:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 01:33:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-09 01:33:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-09 01:33:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-09 01:33:56 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 01:33:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-09 01:33:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-09 01:33:56 (9251) [INFO]         or
* 2024-12-09 01:33:56 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 01:33:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 01:33:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 01:33:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 01:33:56 (9251) [INFO]         compromise:
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-09 01:33:56 (9251) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-09 01:33:56 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-09 01:33:56 (9268) [INFO] 
* 2024-12-09 01:33:56 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-09 01:33:56 (5803) [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-12-09 01:33:56 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-09 01:33:57 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-09 01:33:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FHM0NqTmnp/ea_profile.json
* 2024-12-09 01:33:59 (484) [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/FHM0NqTmnp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-09 01:33:59 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-10 01:33:25 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-10 01:33:25 (10313) [INFO] Script is up to date.
* 2024-12-10 01:33:26 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-10 01:33:26 (6225) [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-12-10 01:33:26 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-10 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-10 01:33:26 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-10 01:33:26 (9238) [INFO] 
* 2024-12-10 01:33:31 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-10 01:33:31 (3970) [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.

* 2024-12-10 01:33:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-10 01:33:31 (9238) [INFO] 
* 2024-12-10 01:33:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-10 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-10 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-10 01:33:49 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-10 01:33:49 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-10 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-10 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-10 01:33:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-10 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-10 01:33:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-10 01:33:49 (9238) [INFO] 
* 2024-12-10 01:33:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 01:33:49 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-10 01:33:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-10 01:33:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-10 01:33:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-10 01:33:51 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-10 01:33:51 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-10 01:33:51 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-10 01:33:51 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-10 01:33:53 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-10 01:33:53 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-10 01:33:53 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-10 01:33:53 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-10 01:33:53 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-10 01:33:53 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-10 01:33:53 (9251) [INFO] Trying other mirror.
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-10 01:33:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 01:33:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 01:33:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-10 01:33:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-10 01:33:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-10 01:33:53 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 01:33:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-10 01:33:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-10 01:33:53 (9251) [INFO]         or
* 2024-12-10 01:33:53 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 01:33:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 01:33:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 01:33:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 01:33:53 (9251) [INFO]         compromise:
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-10 01:33:53 (9251) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-10 01:33:53 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-10 01:33:53 (9268) [INFO] 
* 2024-12-10 01:33:53 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-10 01:33:53 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-10 01:33:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-10 01:33:53 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-10 01:33:53 (9238) [INFO] 
* 2024-12-10 01:33:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 01:33:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-10 01:33:54 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-10 01:33:54 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-10 01:33:54 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-10 01:33:54 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-10 01:33:54 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-10 01:33:54 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-10 01:33:54 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-10 01:33:54 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-10 01:33:54 (9251) [INFO]               : yarn
* 2024-12-10 01:33:54 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-10 01:33:54 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-10 01:33:54 (9268) [INFO] 
* 2024-12-10 01:33:54 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-10 01:33:54 (9238) [INFO] 
* 2024-12-10 01:33:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 01:33:55 (9251) [INFO] Determining fastest mirrors
* 2024-12-10 01:33:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-10 01:33:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-10 01:33:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-10 01:33:59 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-10 01:33:59 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-10 01:33:59 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-10 01:33:59 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-10 01:34:01 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-10 01:34:02 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-10 01:34:02 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-10 01:34:02 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-10 01:34:02 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-10 01:34:02 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-10 01:34:02 (9251) [INFO] Trying other mirror.
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-10 01:34:02 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 01:34:02 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 01:34:02 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-10 01:34:02 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-10 01:34:02 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-10 01:34:02 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 01:34:02 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-10 01:34:02 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-10 01:34:02 (9251) [INFO]         or
* 2024-12-10 01:34:02 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 01:34:02 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 01:34:02 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 01:34:02 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 01:34:02 (9251) [INFO]         compromise:
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-10 01:34:02 (9251) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-10 01:34:02 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-10 01:34:02 (9268) [INFO] 
* 2024-12-10 01:34:02 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-10 01:34:02 (5803) [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-12-10 01:34:02 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-10 01:34:02 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-10 01:34:03 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LywISNLshK/ea_profile.json
* 2024-12-10 01:34:09 (484) [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/LywISNLshK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-10 01:34:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-11 01:34:04 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-11 01:34:04 (10313) [INFO] Script is up to date.
* 2024-12-11 01:34:06 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-11 01:34:06 (6225) [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-12-11 01:34:06 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-11 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-11 01:34:08 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-11 01:34:08 (9238) [INFO] 
* 2024-12-11 01:34:13 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-11 01:34:13 (3970) [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.

* 2024-12-11 01:34:13 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-11 01:34:13 (9238) [INFO] 
* 2024-12-11 01:34:25 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-11 01:34:25 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-11 01:34:25 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-11 01:34:25 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-11 01:34:25 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-11 01:34:25 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-11 01:34:25 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-11 01:34:25 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-11 01:34:25 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-11 01:34:25 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-11 01:34:25 (9238) [INFO] 
* 2024-12-11 01:34:25 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 01:34:25 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-11 01:34:27 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-11 01:34:27 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-11 01:34:27 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-11 01:34:27 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-11 01:34:27 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-11 01:34:27 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-11 01:34:27 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-11 01:34:29 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-11 01:34:29 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-11 01:34:29 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-11 01:34:29 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-11 01:34:29 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-11 01:34:29 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-11 01:34:29 (9251) [INFO] Trying other mirror.
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-11 01:34:29 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 01:34:29 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 01:34:29 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-11 01:34:29 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-11 01:34:29 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-11 01:34:29 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 01:34:29 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-11 01:34:29 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-11 01:34:29 (9251) [INFO]         or
* 2024-12-11 01:34:29 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 01:34:29 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 01:34:29 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 01:34:29 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 01:34:29 (9251) [INFO]         compromise:
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-11 01:34:29 (9251) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-11 01:34:29 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-11 01:34:29 (9268) [INFO] 
* 2024-12-11 01:34:29 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-11 01:34:29 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-11 01:34:29 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-11 01:34:29 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-11 01:34:29 (9238) [INFO] 
* 2024-12-11 01:34:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 01:34:30 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-11 01:34:30 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-11 01:34:30 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-11 01:34:30 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-11 01:34:30 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-11 01:34:30 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-11 01:34:30 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-11 01:34:30 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-11 01:34:30 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-11 01:34:30 (9251) [INFO]               : yarn
* 2024-12-11 01:34:30 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-11 01:34:30 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-11 01:34:30 (9268) [INFO] 
* 2024-12-11 01:34:30 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-11 01:34:30 (9238) [INFO] 
* 2024-12-11 01:34:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 01:34:30 (9251) [INFO] Determining fastest mirrors
* 2024-12-11 01:34:35 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-11 01:34:35 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-11 01:34:35 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-11 01:34:35 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-11 01:34:35 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-11 01:34:35 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-11 01:34:35 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-11 01:34:37 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-11 01:34:38 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-11 01:34:38 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-11 01:34:38 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-11 01:34:38 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-11 01:34:38 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-11 01:34:38 (9251) [INFO] Trying other mirror.
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-11 01:34:38 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 01:34:38 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 01:34:38 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-11 01:34:38 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-11 01:34:38 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-11 01:34:38 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 01:34:38 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-11 01:34:38 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-11 01:34:38 (9251) [INFO]         or
* 2024-12-11 01:34:38 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 01:34:38 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 01:34:38 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 01:34:38 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 01:34:38 (9251) [INFO]         compromise:
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-11 01:34:38 (9251) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-11 01:34:38 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-11 01:34:38 (9268) [INFO] 
* 2024-12-11 01:34:38 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-11 01:34:38 (5803) [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-12-11 01:34:38 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-11 01:34:38 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-11 01:34:39 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qnSApC1B_W/ea_profile.json
* 2024-12-11 01:34:42 (484) [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/qnSApC1B_W/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-11 01:34:42 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-12 01:33:26 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-12 01:33:26 (10313) [INFO] Script is up to date.
* 2024-12-12 01:33:27 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-12 01:33:27 (6225) [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-12-12 01:33:27 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-12 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-12 01:33:28 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-12 01:33:28 (9238) [INFO] 
* 2024-12-12 01:33:32 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-12 01:33:32 (3970) [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.

* 2024-12-12 01:33:32 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-12 01:33:32 (9238) [INFO] 
* 2024-12-12 01:33:51 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-12 01:33:51 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-12 01:33:51 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-12 01:33:51 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-12 01:33:51 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-12 01:33:51 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-12 01:33:51 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-12 01:33:51 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-12 01:33:51 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-12 01:33:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-12 01:33:51 (9238) [INFO] 
* 2024-12-12 01:33:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 01:33:51 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-12 01:33:52 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-12 01:33:52 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-12 01:33:52 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-12 01:33:52 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-12 01:33:52 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-12 01:33:52 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-12 01:33:52 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-12 01:33:55 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-12 01:33:55 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-12 01:33:55 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-12 01:33:55 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-12 01:33:55 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-12 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-12 01:33:55 (9251) [INFO] Trying other mirror.
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-12 01:33:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 01:33:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 01:33:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-12 01:33:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-12 01:33:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-12 01:33:55 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 01:33:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-12 01:33:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-12 01:33:55 (9251) [INFO]         or
* 2024-12-12 01:33:55 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 01:33:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 01:33:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 01:33:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 01:33:55 (9251) [INFO]         compromise:
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-12 01:33:55 (9251) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-12 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-12 01:33:55 (9268) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-12 01:33:55 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-12 01:33:55 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-12 01:33:55 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-12 01:33:55 (9238) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 01:33:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-12 01:33:55 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-12 01:33:55 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-12 01:33:55 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-12 01:33:55 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-12 01:33:55 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-12 01:33:55 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-12 01:33:55 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-12 01:33:55 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-12 01:33:55 (9251) [INFO]               : yarn
* 2024-12-12 01:33:55 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-12 01:33:55 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-12 01:33:55 (9268) [INFO] 
* 2024-12-12 01:33:55 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-12 01:33:55 (9238) [INFO] 
* 2024-12-12 01:33:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 01:33:56 (9251) [INFO] Determining fastest mirrors
* 2024-12-12 01:33:59 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-12 01:33:59 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-12 01:33:59 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-12 01:33:59 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-12 01:33:59 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-12 01:33:59 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-12 01:33:59 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-12 01:34:01 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-12 01:34:01 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-12 01:34:01 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-12 01:34:01 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-12 01:34:01 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-12 01:34:01 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-12 01:34:01 (9251) [INFO] Trying other mirror.
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-12 01:34:01 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 01:34:01 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 01:34:01 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-12 01:34:01 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-12 01:34:01 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-12 01:34:01 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 01:34:01 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-12 01:34:01 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-12 01:34:01 (9251) [INFO]         or
* 2024-12-12 01:34:01 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 01:34:01 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 01:34:01 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 01:34:01 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 01:34:01 (9251) [INFO]         compromise:
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-12 01:34:01 (9251) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-12 01:34:01 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-12 01:34:01 (9268) [INFO] 
* 2024-12-12 01:34:01 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-12 01:34:01 (5803) [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-12-12 01:34:01 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-12 01:34:02 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-12 01:34:03 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/T2f7kGboDF/ea_profile.json
* 2024-12-12 01:34:08 (484) [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/T2f7kGboDF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-12 01:34:08 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-13 01:33:26 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-13 01:33:26 (10313) [INFO] Script is up to date.
* 2024-12-13 01:33:27 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-13 01:33:27 (6225) [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-12-13 01:33:27 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-13 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-13 01:33:27 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-13 01:33:27 (9238) [INFO] 
* 2024-12-13 01:33:32 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-13 01:33:32 (3970) [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.

* 2024-12-13 01:33:32 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-13 01:33:32 (9238) [INFO] 
* 2024-12-13 01:33:41 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-13 01:33:41 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-13 01:33:41 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-13 01:33:41 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-13 01:33:41 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-13 01:33:41 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-13 01:33:41 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-13 01:33:41 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-13 01:33:41 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-13 01:33:41 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-13 01:33:41 (9238) [INFO] 
* 2024-12-13 01:33:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 01:33:41 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-13 01:33:42 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-13 01:33:42 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-13 01:33:42 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-13 01:33:42 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-13 01:33:42 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-13 01:33:42 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-13 01:33:42 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-13 01:33:43 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-13 01:33:43 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-13 01:33:43 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-13 01:33:43 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-13 01:33:43 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-13 01:33:43 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-13 01:33:43 (9251) [INFO] Trying other mirror.
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-13 01:33:43 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 01:33:43 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 01:33:43 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-13 01:33:43 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-13 01:33:43 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-13 01:33:43 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 01:33:43 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-13 01:33:43 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-13 01:33:43 (9251) [INFO]         or
* 2024-12-13 01:33:43 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 01:33:43 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 01:33:43 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 01:33:43 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 01:33:43 (9251) [INFO]         compromise:
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-13 01:33:43 (9251) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-13 01:33:43 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-13 01:33:43 (9268) [INFO] 
* 2024-12-13 01:33:43 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-13 01:33:43 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-13 01:33:43 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-13 01:33:43 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-13 01:33:43 (9238) [INFO] 
* 2024-12-13 01:33:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 01:33:44 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-13 01:33:44 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-13 01:33:44 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-13 01:33:44 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-13 01:33:44 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-13 01:33:44 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-13 01:33:44 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-13 01:33:44 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-13 01:33:44 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-13 01:33:44 (9251) [INFO]               : yarn
* 2024-12-13 01:33:44 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-13 01:33:44 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-13 01:33:44 (9268) [INFO] 
* 2024-12-13 01:33:44 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-13 01:33:44 (9238) [INFO] 
* 2024-12-13 01:33:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 01:33:44 (9251) [INFO] Determining fastest mirrors
* 2024-12-13 01:33:48 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-13 01:33:48 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-13 01:33:48 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-13 01:33:48 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-13 01:33:48 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-13 01:33:48 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-13 01:33:48 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-13 01:33:49 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-13 01:33:49 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-13 01:33:49 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-13 01:33:49 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-13 01:33:49 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-13 01:33:49 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-13 01:33:49 (9251) [INFO] Trying other mirror.
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-13 01:33:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 01:33:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 01:33:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-13 01:33:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-13 01:33:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-13 01:33:49 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 01:33:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-13 01:33:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-13 01:33:49 (9251) [INFO]         or
* 2024-12-13 01:33:49 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 01:33:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 01:33:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 01:33:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 01:33:49 (9251) [INFO]         compromise:
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-13 01:33:49 (9251) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-13 01:33:49 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-13 01:33:49 (9268) [INFO] 
* 2024-12-13 01:33:49 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-13 01:33:49 (5803) [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-12-13 01:33:49 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-13 01:33:49 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-13 01:33:51 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y77JztxOM5/ea_profile.json
* 2024-12-13 01:33:53 (484) [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/y77JztxOM5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-13 01:33:53 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-14 01:34:02 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-14 01:34:02 (10313) [INFO] Script is up to date.
* 2024-12-14 01:34:03 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-14 01:34:04 (6225) [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-12-14 01:34:04 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-14 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-14 01:34:08 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-14 01:34:08 (9238) [INFO] 
* 2024-12-14 01:34:13 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-14 01:34:13 (3970) [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.

* 2024-12-14 01:34:13 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-14 01:34:13 (9238) [INFO] 
* 2024-12-14 01:34:19 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-14 01:34:19 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-14 01:34:19 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-14 01:34:19 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-14 01:34:19 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-14 01:34:19 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-14 01:34:19 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-14 01:34:19 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-14 01:34:19 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-14 01:34:19 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-14 01:34:19 (9238) [INFO] 
* 2024-12-14 01:34:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 01:34:20 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-14 01:34:21 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-14 01:34:21 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-14 01:34:21 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-14 01:34:21 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-14 01:34:21 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-14 01:34:21 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-14 01:34:21 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-14 01:34:23 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-14 01:34:23 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-14 01:34:23 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-14 01:34:23 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-14 01:34:23 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-14 01:34:23 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-14 01:34:23 (9251) [INFO] Trying other mirror.
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-14 01:34:23 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 01:34:23 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 01:34:23 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-14 01:34:23 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-14 01:34:23 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-14 01:34:23 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 01:34:23 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-14 01:34:23 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-14 01:34:23 (9251) [INFO]         or
* 2024-12-14 01:34:23 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 01:34:23 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 01:34:23 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 01:34:23 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 01:34:23 (9251) [INFO]         compromise:
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-14 01:34:23 (9251) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-14 01:34:23 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-14 01:34:23 (9268) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-14 01:34:23 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-14 01:34:23 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-14 01:34:23 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-14 01:34:23 (9238) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 01:34:23 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-14 01:34:23 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-14 01:34:23 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-14 01:34:23 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-14 01:34:23 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-14 01:34:23 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-14 01:34:23 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-14 01:34:23 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-14 01:34:23 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-14 01:34:23 (9251) [INFO]               : yarn
* 2024-12-14 01:34:23 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-14 01:34:23 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-14 01:34:23 (9268) [INFO] 
* 2024-12-14 01:34:23 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-14 01:34:23 (9238) [INFO] 
* 2024-12-14 01:34:23 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 01:34:24 (9251) [INFO] Determining fastest mirrors
* 2024-12-14 01:34:26 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-14 01:34:26 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-14 01:34:26 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-14 01:34:26 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-14 01:34:26 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-14 01:34:26 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-14 01:34:26 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-14 01:34:28 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-14 01:34:28 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-14 01:34:28 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-14 01:34:28 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-14 01:34:28 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-14 01:34:28 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-14 01:34:28 (9251) [INFO] Trying other mirror.
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-14 01:34:28 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 01:34:28 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 01:34:28 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-14 01:34:28 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-14 01:34:28 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-14 01:34:28 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 01:34:28 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-14 01:34:28 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-14 01:34:28 (9251) [INFO]         or
* 2024-12-14 01:34:28 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 01:34:28 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 01:34:28 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 01:34:28 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 01:34:28 (9251) [INFO]         compromise:
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-14 01:34:28 (9251) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-14 01:34:28 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-14 01:34:28 (9268) [INFO] 
* 2024-12-14 01:34:28 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-14 01:34:28 (5803) [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-12-14 01:34:28 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-14 01:34:28 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-14 01:34:30 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1WQyq8VbN6/ea_profile.json
* 2024-12-14 01:34:33 (484) [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/1WQyq8VbN6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-14 01:34:33 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-15 01:34:04 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-15 01:34:04 (10313) [INFO] Script is up to date.
* 2024-12-15 01:34:06 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-15 01:34:06 (6225) [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-12-15 01:34:06 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-15 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-15 01:34:08 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-15 01:34:08 (9238) [INFO] 
* 2024-12-15 01:34:13 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-15 01:34:13 (3970) [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.

* 2024-12-15 01:34:13 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-15 01:34:13 (9238) [INFO] 
* 2024-12-15 01:34:26 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-15 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-15 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-15 01:34:26 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-15 01:34:26 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-15 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-15 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-15 01:34:26 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-15 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-15 01:34:26 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-15 01:34:26 (9238) [INFO] 
* 2024-12-15 01:34:26 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 01:34:26 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-15 01:34:28 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-15 01:34:28 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-15 01:34:28 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-15 01:34:28 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-15 01:34:28 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-15 01:34:28 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-15 01:34:28 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-15 01:34:29 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-15 01:34:29 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-15 01:34:29 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-15 01:34:29 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-15 01:34:29 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-15 01:34:29 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-15 01:34:29 (9251) [INFO] Trying other mirror.
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-15 01:34:29 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 01:34:29 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 01:34:29 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-15 01:34:29 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-15 01:34:29 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-15 01:34:29 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 01:34:29 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-15 01:34:29 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-15 01:34:29 (9251) [INFO]         or
* 2024-12-15 01:34:29 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 01:34:29 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 01:34:29 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 01:34:29 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 01:34:29 (9251) [INFO]         compromise:
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-15 01:34:29 (9251) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-15 01:34:29 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-15 01:34:29 (9268) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-15 01:34:29 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-15 01:34:29 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-15 01:34:29 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-15 01:34:29 (9238) [INFO] 
* 2024-12-15 01:34:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 01:34:30 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-15 01:34:30 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-15 01:34:30 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-15 01:34:30 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-15 01:34:30 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-15 01:34:30 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-15 01:34:30 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-15 01:34:30 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-15 01:34:30 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-15 01:34:30 (9251) [INFO]               : yarn
* 2024-12-15 01:34:30 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-15 01:34:30 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-15 01:34:30 (9268) [INFO] 
* 2024-12-15 01:34:30 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-15 01:34:30 (9238) [INFO] 
* 2024-12-15 01:34:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 01:34:30 (9251) [INFO] Determining fastest mirrors
* 2024-12-15 01:34:32 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-15 01:34:32 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-15 01:34:32 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-15 01:34:32 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-15 01:34:32 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-15 01:34:32 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-15 01:34:32 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-15 01:34:34 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-15 01:34:34 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-15 01:34:34 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-15 01:34:34 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-15 01:34:34 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-15 01:34:34 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-15 01:34:34 (9251) [INFO] Trying other mirror.
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-15 01:34:34 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 01:34:34 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 01:34:34 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-15 01:34:34 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-15 01:34:34 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-15 01:34:34 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 01:34:34 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-15 01:34:34 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-15 01:34:34 (9251) [INFO]         or
* 2024-12-15 01:34:34 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 01:34:34 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 01:34:34 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 01:34:34 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 01:34:34 (9251) [INFO]         compromise:
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-15 01:34:34 (9251) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-15 01:34:34 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-15 01:34:34 (9268) [INFO] 
* 2024-12-15 01:34:34 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-15 01:34:34 (5803) [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-12-15 01:34:34 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-15 01:34:35 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-15 01:34:36 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GzjLu57GBQ/ea_profile.json
* 2024-12-15 01:34:40 (484) [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/GzjLu57GBQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-15 01:34:40 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-16 01:33:22 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-16 01:33:22 (10313) [INFO] Script is up to date.
* 2024-12-16 01:33:23 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-16 01:33:23 (6225) [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-12-16 01:33:23 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-16 01:33:23 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-16 01:33:23 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-16 01:33:23 (9238) [INFO] 
* 2024-12-16 01:33:28 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-16 01:33:28 (3970) [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.

* 2024-12-16 01:33:28 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-16 01:33:28 (9238) [INFO] 
* 2024-12-16 01:33:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-16 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-16 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-16 01:33:44 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-16 01:33:44 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-16 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-16 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-16 01:33:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-16 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-16 01:33:44 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-16 01:33:44 (9238) [INFO] 
* 2024-12-16 01:33:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 01:33:44 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-16 01:33:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-16 01:33:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-16 01:33:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-16 01:33:46 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-16 01:33:46 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-16 01:33:46 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-16 01:33:46 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-16 01:33:47 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-16 01:33:47 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-16 01:33:47 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-16 01:33:47 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-16 01:33:47 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-16 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-16 01:33:47 (9251) [INFO] Trying other mirror.
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-16 01:33:47 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 01:33:47 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 01:33:47 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-16 01:33:47 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-16 01:33:47 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-16 01:33:47 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 01:33:47 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-16 01:33:47 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-16 01:33:47 (9251) [INFO]         or
* 2024-12-16 01:33:47 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 01:33:47 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 01:33:47 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 01:33:47 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 01:33:47 (9251) [INFO]         compromise:
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-16 01:33:47 (9251) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-16 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-16 01:33:47 (9268) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-16 01:33:47 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-16 01:33:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-16 01:33:47 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-16 01:33:47 (9238) [INFO] 
* 2024-12-16 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 01:33:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-16 01:33:48 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-16 01:33:48 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-16 01:33:48 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-16 01:33:48 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-16 01:33:48 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-16 01:33:48 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-16 01:33:48 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-16 01:33:48 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-16 01:33:48 (9251) [INFO]               : yarn
* 2024-12-16 01:33:48 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-16 01:33:48 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-16 01:33:48 (9268) [INFO] 
* 2024-12-16 01:33:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-16 01:33:48 (9238) [INFO] 
* 2024-12-16 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 01:33:48 (9251) [INFO] Determining fastest mirrors
* 2024-12-16 01:33:53 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-16 01:33:53 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-16 01:33:53 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-16 01:33:53 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-16 01:33:53 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-16 01:33:53 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-16 01:33:53 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-16 01:33:55 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-16 01:33:55 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-16 01:33:55 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-16 01:33:55 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-16 01:33:55 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-16 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-16 01:33:55 (9251) [INFO] Trying other mirror.
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-16 01:33:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 01:33:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 01:33:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-16 01:33:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-16 01:33:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-16 01:33:55 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 01:33:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-16 01:33:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-16 01:33:55 (9251) [INFO]         or
* 2024-12-16 01:33:55 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 01:33:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 01:33:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 01:33:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 01:33:55 (9251) [INFO]         compromise:
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-16 01:33:55 (9251) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-16 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-16 01:33:55 (9268) [INFO] 
* 2024-12-16 01:33:55 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-16 01:33:55 (5803) [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-12-16 01:33:55 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-16 01:33:55 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-16 01:33:56 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AwMHdksj9u/ea_profile.json
* 2024-12-16 01:34:00 (484) [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/AwMHdksj9u/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-16 01:34:00 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-17 01:33:24 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-17 01:33:24 (10313) [INFO] Script is up to date.
* 2024-12-17 01:33:26 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-17 01:33:26 (6225) [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-12-17 01:33:26 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-17 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-17 01:33:26 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-17 01:33:26 (9238) [INFO] 
* 2024-12-17 01:33:30 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-17 01:33:30 (3970) [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.

* 2024-12-17 01:33:30 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-17 01:33:30 (9238) [INFO] 
* 2024-12-17 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-17 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-17 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-17 01:33:39 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-17 01:33:39 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-17 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-17 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-17 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-17 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-17 01:33:39 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-17 01:33:39 (9238) [INFO] 
* 2024-12-17 01:33:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 01:33:39 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-17 01:33:41 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-17 01:33:41 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-17 01:33:41 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-17 01:33:41 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-17 01:33:41 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2024-12-17 01:33:41 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2024-12-17 01:33:41 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2024-12-17 01:33:42 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-17 01:33:42 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-17 01:33:42 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-17 01:33:42 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-17 01:33:42 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-17 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-17 01:33:42 (9251) [INFO] Trying other mirror.
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-17 01:33:42 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 01:33:42 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 01:33:42 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-17 01:33:42 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-17 01:33:42 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-17 01:33:42 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 01:33:42 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-17 01:33:42 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-17 01:33:42 (9251) [INFO]         or
* 2024-12-17 01:33:42 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 01:33:42 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 01:33:42 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 01:33:42 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 01:33:42 (9251) [INFO]         compromise:
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-17 01:33:42 (9251) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-17 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-17 01:33:42 (9268) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-17 01:33:42 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-17 01:33:42 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-17 01:33:42 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-17 01:33:42 (9238) [INFO] 
* 2024-12-17 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 01:33:43 (9251) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 335828.
* 2024-12-17 01:33:43 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-17 01:33:43 (9251) [INFO]   The other application is: yum
* 2024-12-17 01:33:43 (9251) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2024-12-17 01:33:43 (9251) [INFO]     Started: Tue Dec 17 01:33:34 2024 - 00:09 ago
* 2024-12-17 01:33:43 (9251) [INFO]     State  : Sleeping, pid: 335828
* 2024-12-17 01:33:45 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-12-17 01:33:45 (9251) [INFO]   The other application is: yum
* 2024-12-17 01:33:45 (9251) [INFO]     Memory :  38 M RSS (332 MB VSZ)
* 2024-12-17 01:33:45 (9251) [INFO]     Started: Tue Dec 17 01:33:34 2024 - 00:11 ago
* 2024-12-17 01:33:45 (9251) [INFO]     State  : Sleeping, pid: 335828
* 2024-12-17 01:33:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-17 01:33:47 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-17 01:33:47 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-17 01:33:47 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-17 01:33:47 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-17 01:33:47 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-17 01:33:47 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-17 01:33:47 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-17 01:33:47 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-17 01:33:47 (9251) [INFO]               : yarn
* 2024-12-17 01:33:47 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-17 01:33:47 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-17 01:33:47 (9268) [INFO] 
* 2024-12-17 01:33:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-17 01:33:47 (9238) [INFO] 
* 2024-12-17 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 01:33:47 (9251) [INFO] Determining fastest mirrors
* 2024-12-17 01:33:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-17 01:33:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-17 01:33:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-17 01:33:51 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-17 01:33:51 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-17 01:33:51 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-17 01:33:51 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-17 01:33:52 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-17 01:33:53 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-17 01:33:53 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-17 01:33:53 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-17 01:33:53 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-17 01:33:53 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-17 01:33:53 (9251) [INFO] Trying other mirror.
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-17 01:33:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 01:33:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 01:33:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-17 01:33:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-17 01:33:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-17 01:33:53 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 01:33:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-17 01:33:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-17 01:33:53 (9251) [INFO]         or
* 2024-12-17 01:33:53 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 01:33:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 01:33:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 01:33:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 01:33:53 (9251) [INFO]         compromise:
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-17 01:33:53 (9251) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-17 01:33:53 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-17 01:33:53 (9268) [INFO] 
* 2024-12-17 01:33:53 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-17 01:33:53 (5803) [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-12-17 01:33:53 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-17 01:33:53 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-17 01:33:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/02LO7es6JY/ea_profile.json
* 2024-12-17 01:33:58 (484) [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/02LO7es6JY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-17 01:33:58 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-18 01:33:24 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-18 01:33:24 (10313) [INFO] Script is up to date.
* 2024-12-18 01:33:25 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-18 01:33:25 (6225) [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-12-18 01:33:25 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-18 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-18 01:33:25 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-18 01:33:25 (9238) [INFO] 
* 2024-12-18 01:33:30 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-18 01:33:30 (3970) [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.

* 2024-12-18 01:33:30 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-18 01:33:30 (9238) [INFO] 
* 2024-12-18 01:33:40 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-18 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-18 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-18 01:33:40 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-18 01:33:40 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-18 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-18 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-18 01:33:40 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-18 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-18 01:33:40 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-18 01:33:40 (9238) [INFO] 
* 2024-12-18 01:33:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 01:33:40 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-18 01:33:41 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-18 01:33:41 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-18 01:33:41 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-18 01:33:41 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-18 01:33:41 (9251) [INFO]  * remi-php72: rpms.remirepo.net
* 2024-12-18 01:33:41 (9251) [INFO]  * remi-php73: rpms.remirepo.net
* 2024-12-18 01:33:41 (9251) [INFO]  * remi-safe: rpms.remirepo.net
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]  One of the configured repositories failed (Unknown),
* 2024-12-18 01:33:42 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 01:33:42 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 01:33:42 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-18 01:33:42 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-18 01:33:42 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-18 01:33:42 (9251) [INFO]             yum --disablerepo=<repoid> ...
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 01:33:42 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-18 01:33:42 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]             yum-config-manager --disable <repoid>
* 2024-12-18 01:33:42 (9251) [INFO]         or
* 2024-12-18 01:33:42 (9251) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 01:33:42 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 01:33:42 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 01:33:42 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 01:33:42 (9251) [INFO]         compromise:
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-18 01:33:42 (9251) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2024-12-18 01:33:42 (9251) [INFO]     * free   0 
* 2024-12-18 01:33:42 (9251) [INFO]     * needed 100 k
* 2024-12-18 01:33:42 (9268) [INFO] 
* 2024-12-18 01:33:42 (5793) [WARN] Initial run of "yum makecache" failed: 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-12-18 01:33:42 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-18 01:33:42 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-18 01:33:42 (9238) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 01:33:42 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-18 01:33:42 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-18 01:33:42 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-18 01:33:42 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-18 01:33:42 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-18 01:33:42 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-18 01:33:42 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-18 01:33:42 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-18 01:33:42 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-18 01:33:42 (9251) [INFO]               : yarn
* 2024-12-18 01:33:42 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-18 01:33:42 (9251) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-12-18 01:33:42 (9268) [INFO] 
* 2024-12-18 01:33:42 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-18 01:33:42 (9238) [INFO] 
* 2024-12-18 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 01:33:42 (9251) [INFO] Determining fastest mirrors
* 2024-12-18 01:33:45 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-18 01:33:45 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-18 01:33:45 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-18 01:33:45 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-18 01:33:45 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-18 01:33:45 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-18 01:33:45 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]  One of the configured repositories failed (Unknown),
* 2024-12-18 01:33:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 01:33:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 01:33:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-18 01:33:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-18 01:33:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-18 01:33:45 (9251) [INFO]             yum --disablerepo=<repoid> ...
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 01:33:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-18 01:33:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]             yum-config-manager --disable <repoid>
* 2024-12-18 01:33:45 (9251) [INFO]         or
* 2024-12-18 01:33:45 (9251) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 01:33:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 01:33:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 01:33:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 01:33:45 (9251) [INFO]         compromise:
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-18 01:33:45 (9251) [INFO] 
* 2024-12-18 01:33:45 (9251) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2024-12-18 01:33:45 (9251) [INFO]     * free   0 
* 2024-12-18 01:33:45 (9251) [INFO]     * needed 100 k
* 2024-12-18 01:33:45 (9268) [INFO] 
* 2024-12-18 01:33:45 (5803) [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-12-18 01:33:45 (5804) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-12-18 01:33:45 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-18 01:33:47 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ghk3Kjrw4X/ea_profile.json
* 2024-12-18 01:33:47 (484) [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/Ghk3Kjrw4X/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-18 01:33:47 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-19 01:33:30 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-19 01:33:30 (10313) [INFO] Script is up to date.
* 2024-12-19 01:33:31 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-19 01:33:31 (6225) [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-12-19 01:33:31 (252) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2024-12-19 01:33:31 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-19 01:33:31 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-19 01:33:31 (9238) [INFO] 
* 2024-12-19 01:33:35 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-19 01:33:35 (3970) [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.

* 2024-12-19 01:33:35 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-19 01:33:35 (9238) [INFO] 
* 2024-12-19 01:33:40 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-19 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-19 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-19 01:33:40 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-19 01:33:40 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-19 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-19 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-19 01:33:40 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-19 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-19 01:33:40 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-19 01:33:40 (9238) [INFO] 
* 2024-12-19 01:33:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 01:33:41 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-19 01:33:42 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-19 01:33:42 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-19 01:33:42 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-19 01:33:42 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-19 01:33:42 (9251) [INFO]  * remi-php72: remi.mirror.ate.info
* 2024-12-19 01:33:42 (9251) [INFO]  * remi-php73: remi.mirror.ate.info
* 2024-12-19 01:33:42 (9251) [INFO]  * remi-safe: remi.mirror.ate.info
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]  One of the configured repositories failed (Unknown),
* 2024-12-19 01:33:42 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 01:33:42 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 01:33:42 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-19 01:33:42 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-19 01:33:42 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-19 01:33:42 (9251) [INFO]             yum --disablerepo=<repoid> ...
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 01:33:42 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-19 01:33:42 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]             yum-config-manager --disable <repoid>
* 2024-12-19 01:33:42 (9251) [INFO]         or
* 2024-12-19 01:33:42 (9251) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 01:33:42 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 01:33:42 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 01:33:42 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 01:33:42 (9251) [INFO]         compromise:
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-19 01:33:42 (9251) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2024-12-19 01:33:42 (9251) [INFO]     * free   0 
* 2024-12-19 01:33:42 (9251) [INFO]     * needed 100 k
* 2024-12-19 01:33:42 (9268) [INFO] 
* 2024-12-19 01:33:42 (5793) [WARN] Initial run of "yum makecache" failed: 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-12-19 01:33:42 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-19 01:33:42 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-19 01:33:42 (9238) [INFO] 
* 2024-12-19 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 01:33:42 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-19 01:33:42 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-19 01:33:42 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-19 01:33:42 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-19 01:33:42 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-19 01:33:42 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-19 01:33:42 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-19 01:33:42 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-19 01:33:42 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-19 01:33:42 (9251) [INFO]               : yarn
* 2024-12-19 01:33:42 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-19 01:33:42 (9251) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2024-12-19 01:33:42 (9268) [INFO] 
* 2024-12-19 01:33:42 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-19 01:33:42 (9238) [INFO] 
* 2024-12-19 01:33:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 01:33:43 (9251) [INFO] Determining fastest mirrors
* 2024-12-19 01:33:45 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-19 01:33:45 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-19 01:33:45 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-19 01:33:45 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-19 01:33:45 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-19 01:33:45 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-19 01:33:45 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]  One of the configured repositories failed (Unknown),
* 2024-12-19 01:33:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 01:33:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 01:33:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-19 01:33:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-19 01:33:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-19 01:33:45 (9251) [INFO]             yum --disablerepo=<repoid> ...
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 01:33:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-19 01:33:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]             yum-config-manager --disable <repoid>
* 2024-12-19 01:33:45 (9251) [INFO]         or
* 2024-12-19 01:33:45 (9251) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 01:33:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 01:33:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 01:33:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 01:33:45 (9251) [INFO]         compromise:
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-19 01:33:45 (9251) [INFO] 
* 2024-12-19 01:33:45 (9251) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2024-12-19 01:33:45 (9251) [INFO]     * free   0 
* 2024-12-19 01:33:45 (9251) [INFO]     * needed 100 k
* 2024-12-19 01:33:45 (9268) [INFO] 
* 2024-12-19 01:33:45 (5803) [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-12-19 01:33:45 (5804) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2024-12-19 01:33:45 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-19 01:33:47 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ch3xwyTuuz/ea_profile.json
* 2024-12-19 01:33:48 (484) [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/ch3xwyTuuz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-19 01:33:48 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-20 01:33:32 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-20 01:33:32 (10313) [INFO] Script is up to date.
* 2024-12-20 01:33:34 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-20 01:33:34 (6225) [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-12-20 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-20 01:33:34 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-20 01:33:34 (9238) [INFO] 
* 2024-12-20 01:33:40 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-20 01:33:40 (3970) [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.

* 2024-12-20 01:33:40 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-20 01:33:40 (9238) [INFO] 
* 2024-12-20 01:33:56 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-20 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-20 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-20 01:33:56 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-20 01:33:56 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-20 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-20 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-20 01:33:56 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-20 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-20 01:33:56 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-20 01:33:56 (9238) [INFO] 
* 2024-12-20 01:33:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 01:33:57 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-20 01:33:58 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-20 01:33:58 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-20 01:33:58 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-20 01:33:58 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-20 01:33:58 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2024-12-20 01:33:58 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2024-12-20 01:33:58 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2024-12-20 01:34:00 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-20 01:34:00 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-20 01:34:00 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-20 01:34:00 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-20 01:34:00 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-20 01:34:00 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-20 01:34:00 (9251) [INFO] Trying other mirror.
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-20 01:34:00 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 01:34:00 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 01:34:00 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-20 01:34:00 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-20 01:34:00 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-20 01:34:00 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 01:34:00 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-20 01:34:00 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-20 01:34:00 (9251) [INFO]         or
* 2024-12-20 01:34:00 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 01:34:00 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 01:34:00 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 01:34:00 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 01:34:00 (9251) [INFO]         compromise:
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-20 01:34:00 (9251) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-20 01:34:00 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-20 01:34:00 (9268) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-20 01:34:00 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-20 01:34:00 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-20 01:34:00 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-20 01:34:00 (9238) [INFO] 
* 2024-12-20 01:34:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 01:34:01 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-20 01:34:01 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-20 01:34:01 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-20 01:34:01 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-20 01:34:01 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-20 01:34:01 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-20 01:34:01 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-20 01:34:01 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-20 01:34:01 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-20 01:34:01 (9251) [INFO]               : yarn
* 2024-12-20 01:34:01 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-20 01:34:01 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-20 01:34:01 (9268) [INFO] 
* 2024-12-20 01:34:01 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-20 01:34:01 (9238) [INFO] 
* 2024-12-20 01:34:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 01:34:01 (9251) [INFO] Determining fastest mirrors
* 2024-12-20 01:34:06 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-20 01:34:06 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-20 01:34:06 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-20 01:34:06 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-20 01:34:06 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-20 01:34:06 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-20 01:34:06 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-20 01:34:07 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-20 01:34:07 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-20 01:34:07 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-20 01:34:07 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-20 01:34:07 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-20 01:34:07 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-20 01:34:07 (9251) [INFO] Trying other mirror.
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-20 01:34:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 01:34:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 01:34:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-20 01:34:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-20 01:34:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-20 01:34:07 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 01:34:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-20 01:34:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-20 01:34:07 (9251) [INFO]         or
* 2024-12-20 01:34:07 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 01:34:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 01:34:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 01:34:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 01:34:07 (9251) [INFO]         compromise:
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-20 01:34:07 (9251) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-20 01:34:07 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-20 01:34:07 (9268) [INFO] 
* 2024-12-20 01:34:07 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-20 01:34:07 (5803) [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-12-20 01:34:07 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-20 01:34:07 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-20 01:34:09 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/suCfVwoOdX/ea_profile.json
* 2024-12-20 01:34:12 (484) [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/suCfVwoOdX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-20 01:34:12 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-21 01:33:56 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-21 01:33:57 (10313) [INFO] Script is up to date.
* 2024-12-21 01:33:58 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-21 01:33:58 (6225) [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-12-21 01:33:58 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-21 01:33:58 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-21 01:33:58 (9238) [INFO] 
* 2024-12-21 01:34:03 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-21 01:34:03 (3970) [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.

* 2024-12-21 01:34:03 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-21 01:34:03 (9238) [INFO] 
* 2024-12-21 01:34:15 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-21 01:34:15 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-21 01:34:15 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-21 01:34:15 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-21 01:34:15 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-21 01:34:15 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-21 01:34:15 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-21 01:34:15 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-21 01:34:15 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-21 01:34:15 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-21 01:34:15 (9238) [INFO] 
* 2024-12-21 01:34:15 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 01:34:15 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-21 01:34:16 (9251) [INFO]  * EA4: 63.247.64.58
* 2024-12-21 01:34:16 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-12-21 01:34:16 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-12-21 01:34:16 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-21 01:34:16 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-21 01:34:16 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-21 01:34:16 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-21 01:34:17 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-21 01:34:18 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-21 01:34:18 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-21 01:34:18 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-21 01:34:18 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-21 01:34:18 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-21 01:34:18 (9251) [INFO] Trying other mirror.
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-21 01:34:18 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 01:34:18 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 01:34:18 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-21 01:34:18 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-21 01:34:18 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-21 01:34:18 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 01:34:18 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-21 01:34:18 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-21 01:34:18 (9251) [INFO]         or
* 2024-12-21 01:34:18 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 01:34:18 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 01:34:18 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 01:34:18 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 01:34:18 (9251) [INFO]         compromise:
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-21 01:34:18 (9251) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-21 01:34:18 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-21 01:34:18 (9268) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-21 01:34:18 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-21 01:34:18 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-21 01:34:18 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-21 01:34:18 (9238) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 01:34:18 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-21 01:34:18 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-21 01:34:18 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-21 01:34:18 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-21 01:34:18 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-21 01:34:18 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-21 01:34:18 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-21 01:34:18 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-21 01:34:18 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-21 01:34:18 (9251) [INFO]               : yarn
* 2024-12-21 01:34:18 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-21 01:34:18 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-21 01:34:18 (9268) [INFO] 
* 2024-12-21 01:34:18 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-21 01:34:18 (9238) [INFO] 
* 2024-12-21 01:34:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 01:34:19 (9251) [INFO] Determining fastest mirrors
* 2024-12-21 01:34:20 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-21 01:34:20 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-21 01:34:20 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-21 01:34:20 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-21 01:34:20 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-21 01:34:20 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-21 01:34:20 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-21 01:34:21 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-21 01:34:22 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-21 01:34:22 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-21 01:34:22 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-21 01:34:22 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-21 01:34:22 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-21 01:34:22 (9251) [INFO] Trying other mirror.
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-21 01:34:22 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 01:34:22 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 01:34:22 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-21 01:34:22 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-21 01:34:22 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-21 01:34:22 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 01:34:22 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-21 01:34:22 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-21 01:34:22 (9251) [INFO]         or
* 2024-12-21 01:34:22 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 01:34:22 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 01:34:22 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 01:34:22 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 01:34:22 (9251) [INFO]         compromise:
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-21 01:34:22 (9251) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-21 01:34:22 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-21 01:34:22 (9268) [INFO] 
* 2024-12-21 01:34:22 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-21 01:34:22 (5803) [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-12-21 01:34:22 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-21 01:34:22 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-21 01:34:24 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R1wtuOetrD/ea_profile.json
* 2024-12-21 01:34:27 (484) [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/R1wtuOetrD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-21 01:34:27 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-22 01:34:16 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-22 01:34:16 (10313) [INFO] Script is up to date.
* 2024-12-22 01:34:18 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-22 01:34:18 (6225) [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-12-22 01:34:18 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-22 01:34:18 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-22 01:34:18 (9238) [INFO] 
* 2024-12-22 01:34:25 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-22 01:34:25 (3970) [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.

* 2024-12-22 01:34:25 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-22 01:34:25 (9238) [INFO] 
* 2024-12-22 01:34:32 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-22 01:34:32 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-22 01:34:32 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-22 01:34:32 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-22 01:34:32 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-22 01:34:32 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-22 01:34:32 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-22 01:34:32 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-22 01:34:32 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-22 01:34:32 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-22 01:34:32 (9238) [INFO] 
* 2024-12-22 01:34:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 01:34:32 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-22 01:34:34 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-22 01:34:34 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-22 01:34:34 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-22 01:34:34 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-22 01:34:34 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-22 01:34:34 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-22 01:34:34 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-22 01:34:35 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-22 01:34:35 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-22 01:34:35 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-22 01:34:35 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-22 01:34:35 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-22 01:34:35 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-22 01:34:35 (9251) [INFO] Trying other mirror.
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-22 01:34:35 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 01:34:35 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 01:34:35 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-22 01:34:35 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-22 01:34:35 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-22 01:34:35 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 01:34:35 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-22 01:34:35 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-22 01:34:35 (9251) [INFO]         or
* 2024-12-22 01:34:35 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 01:34:35 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 01:34:35 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 01:34:35 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 01:34:35 (9251) [INFO]         compromise:
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-22 01:34:35 (9251) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-22 01:34:35 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-22 01:34:35 (9268) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-22 01:34:35 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-22 01:34:35 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-22 01:34:35 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-22 01:34:35 (9238) [INFO] 
* 2024-12-22 01:34:35 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 01:34:35 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-22 01:34:35 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-22 01:34:35 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-22 01:34:35 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-22 01:34:35 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-22 01:34:35 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-22 01:34:35 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-22 01:34:35 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-22 01:34:35 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-22 01:34:35 (9251) [INFO]               : yarn
* 2024-12-22 01:34:35 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-22 01:34:35 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-22 01:34:36 (9268) [INFO] 
* 2024-12-22 01:34:36 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-22 01:34:36 (9238) [INFO] 
* 2024-12-22 01:34:36 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 01:34:36 (9251) [INFO] Determining fastest mirrors
* 2024-12-22 01:34:40 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-22 01:34:40 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-22 01:34:40 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-22 01:34:40 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-22 01:34:40 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-22 01:34:40 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-22 01:34:40 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-22 01:34:41 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-22 01:34:41 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-22 01:34:41 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-22 01:34:41 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-22 01:34:41 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-22 01:34:41 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-22 01:34:41 (9251) [INFO] Trying other mirror.
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-22 01:34:41 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 01:34:41 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 01:34:41 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-22 01:34:41 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-22 01:34:41 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-22 01:34:41 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 01:34:41 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-22 01:34:41 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-22 01:34:41 (9251) [INFO]         or
* 2024-12-22 01:34:41 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 01:34:41 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 01:34:41 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 01:34:41 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 01:34:41 (9251) [INFO]         compromise:
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-22 01:34:41 (9251) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-22 01:34:41 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-22 01:34:41 (9268) [INFO] 
* 2024-12-22 01:34:41 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-22 01:34:41 (5803) [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-12-22 01:34:41 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-22 01:34:41 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-22 01:34:43 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iQfzKdUapd/ea_profile.json
* 2024-12-22 01:34:46 (484) [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/iQfzKdUapd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-22 01:34:46 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-23 01:33:23 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-23 01:33:23 (10313) [INFO] Script is up to date.
* 2024-12-23 01:33:24 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-23 01:33:24 (6225) [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-12-23 01:33:24 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-23 01:33:24 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-23 01:33:24 (9238) [INFO] 
* 2024-12-23 01:33:28 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-23 01:33:28 (3970) [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.

* 2024-12-23 01:33:28 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-23 01:33:28 (9238) [INFO] 
* 2024-12-23 01:33:40 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-23 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-23 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-23 01:33:40 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-23 01:33:40 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-23 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-23 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-23 01:33:40 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-23 01:33:40 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-23 01:33:40 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-23 01:33:40 (9238) [INFO] 
* 2024-12-23 01:33:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 01:33:40 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-23 01:33:41 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-23 01:33:41 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-23 01:33:41 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-23 01:33:41 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-23 01:33:41 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-23 01:33:41 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-23 01:33:41 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-23 01:33:41 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-23 01:33:42 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-23 01:33:42 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-23 01:33:42 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-23 01:33:42 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-23 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-23 01:33:42 (9251) [INFO] Trying other mirror.
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-23 01:33:42 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 01:33:42 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 01:33:42 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-23 01:33:42 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-23 01:33:42 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-23 01:33:42 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 01:33:42 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-23 01:33:42 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-23 01:33:42 (9251) [INFO]         or
* 2024-12-23 01:33:42 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 01:33:42 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 01:33:42 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 01:33:42 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 01:33:42 (9251) [INFO]         compromise:
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-23 01:33:42 (9251) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-23 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-23 01:33:42 (9268) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-23 01:33:42 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-23 01:33:42 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-23 01:33:42 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-23 01:33:42 (9238) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 01:33:42 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-23 01:33:42 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-23 01:33:42 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-23 01:33:42 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-23 01:33:42 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-23 01:33:42 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-23 01:33:42 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-23 01:33:42 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-23 01:33:42 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-23 01:33:42 (9251) [INFO]               : yarn
* 2024-12-23 01:33:42 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-23 01:33:42 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-23 01:33:42 (9268) [INFO] 
* 2024-12-23 01:33:42 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-23 01:33:42 (9238) [INFO] 
* 2024-12-23 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 01:33:42 (9251) [INFO] Determining fastest mirrors
* 2024-12-23 01:33:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-23 01:33:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-23 01:33:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-23 01:33:46 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-23 01:33:46 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-23 01:33:46 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-23 01:33:46 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-23 01:33:47 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-23 01:33:47 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-23 01:33:47 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-23 01:33:47 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-23 01:33:47 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-23 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-23 01:33:47 (9251) [INFO] Trying other mirror.
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-23 01:33:47 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 01:33:47 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 01:33:47 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-23 01:33:47 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-23 01:33:47 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-23 01:33:47 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 01:33:47 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-23 01:33:47 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-23 01:33:47 (9251) [INFO]         or
* 2024-12-23 01:33:47 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 01:33:47 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 01:33:47 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 01:33:47 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 01:33:47 (9251) [INFO]         compromise:
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-23 01:33:47 (9251) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-23 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-23 01:33:47 (9268) [INFO] 
* 2024-12-23 01:33:47 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-23 01:33:47 (5803) [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-12-23 01:33:47 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-23 01:33:47 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-23 01:33:49 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GfgyAtY6TD/ea_profile.json
* 2024-12-23 01:33:52 (484) [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/GfgyAtY6TD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-23 01:33:52 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-24 01:33:31 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-24 01:33:31 (10313) [INFO] Script is up to date.
* 2024-12-24 01:33:32 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-24 01:33:32 (6225) [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-12-24 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-24 01:33:32 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-24 01:33:32 (9238) [INFO] 
* 2024-12-24 01:33:36 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-24 01:33:36 (3970) [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.

* 2024-12-24 01:33:36 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-24 01:33:36 (9238) [INFO] 
* 2024-12-24 01:33:56 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-24 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-24 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-24 01:33:56 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-24 01:33:56 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-24 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-24 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-24 01:33:56 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-24 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-24 01:33:56 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-24 01:33:56 (9238) [INFO] 
* 2024-12-24 01:33:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 01:33:56 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-24 01:33:58 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-24 01:33:58 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-24 01:33:58 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-24 01:33:58 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-24 01:33:58 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-24 01:33:58 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-24 01:33:58 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-24 01:33:59 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-24 01:33:59 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-24 01:33:59 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-24 01:33:59 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-24 01:33:59 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-24 01:33:59 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-24 01:33:59 (9251) [INFO] Trying other mirror.
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-24 01:33:59 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 01:33:59 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 01:33:59 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-24 01:33:59 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-24 01:33:59 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-24 01:33:59 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 01:33:59 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-24 01:33:59 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-24 01:33:59 (9251) [INFO]         or
* 2024-12-24 01:33:59 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 01:33:59 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 01:33:59 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 01:33:59 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 01:33:59 (9251) [INFO]         compromise:
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-24 01:33:59 (9251) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-24 01:33:59 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-24 01:33:59 (9268) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-24 01:33:59 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-24 01:33:59 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-24 01:33:59 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-24 01:33:59 (9238) [INFO] 
* 2024-12-24 01:33:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 01:34:00 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-24 01:34:00 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-24 01:34:00 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-24 01:34:00 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-24 01:34:00 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-24 01:34:00 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-24 01:34:00 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-24 01:34:00 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-24 01:34:00 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-24 01:34:00 (9251) [INFO]               : yarn
* 2024-12-24 01:34:00 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-24 01:34:00 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-24 01:34:00 (9268) [INFO] 
* 2024-12-24 01:34:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-24 01:34:00 (9238) [INFO] 
* 2024-12-24 01:34:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 01:34:00 (9251) [INFO] Determining fastest mirrors
* 2024-12-24 01:34:03 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-24 01:34:03 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-24 01:34:03 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-24 01:34:03 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-24 01:34:03 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-24 01:34:03 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-24 01:34:03 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-24 01:34:04 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-24 01:34:04 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-24 01:34:04 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-24 01:34:04 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-24 01:34:04 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-24 01:34:04 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-24 01:34:04 (9251) [INFO] Trying other mirror.
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-24 01:34:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 01:34:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 01:34:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-24 01:34:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-24 01:34:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-24 01:34:04 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 01:34:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-24 01:34:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-24 01:34:04 (9251) [INFO]         or
* 2024-12-24 01:34:04 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 01:34:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 01:34:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 01:34:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 01:34:04 (9251) [INFO]         compromise:
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-24 01:34:04 (9251) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-24 01:34:04 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-24 01:34:04 (9268) [INFO] 
* 2024-12-24 01:34:04 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-24 01:34:04 (5803) [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-12-24 01:34:04 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-24 01:34:04 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-24 01:34:05 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1k6ulP8FOo/ea_profile.json
* 2024-12-24 01:34:09 (484) [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/1k6ulP8FOo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-24 01:34:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-25 01:33:32 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-25 01:33:32 (10313) [INFO] Script is up to date.
* 2024-12-25 01:33:33 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-25 01:33:33 (6225) [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-12-25 01:33:34 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-25 01:33:34 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-25 01:33:34 (9238) [INFO] 
* 2024-12-25 01:33:39 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-25 01:33:39 (3970) [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.

* 2024-12-25 01:33:39 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-25 01:33:39 (9238) [INFO] 
* 2024-12-25 01:33:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-25 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-25 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-25 01:33:49 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-25 01:33:49 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-25 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-25 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-25 01:33:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-25 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-25 01:33:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-25 01:33:49 (9238) [INFO] 
* 2024-12-25 01:33:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 01:33:49 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-25 01:33:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-25 01:33:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-25 01:33:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-25 01:33:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-25 01:33:50 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2024-12-25 01:33:50 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2024-12-25 01:33:50 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2024-12-25 01:33:51 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-25 01:33:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-25 01:33:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-25 01:33:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-25 01:33:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-25 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-25 01:33:51 (9251) [INFO] Trying other mirror.
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-25 01:33:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 01:33:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 01:33:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-25 01:33:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-25 01:33:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-25 01:33:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 01:33:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-25 01:33:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-25 01:33:51 (9251) [INFO]         or
* 2024-12-25 01:33:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 01:33:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 01:33:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 01:33:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 01:33:51 (9251) [INFO]         compromise:
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-25 01:33:51 (9251) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-25 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-25 01:33:51 (9268) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-25 01:33:51 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-25 01:33:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-25 01:33:51 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-25 01:33:51 (9238) [INFO] 
* 2024-12-25 01:33:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 01:33:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-25 01:33:52 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-25 01:33:52 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-25 01:33:52 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-25 01:33:52 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-25 01:33:52 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-25 01:33:52 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-25 01:33:52 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-25 01:33:52 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-25 01:33:52 (9251) [INFO]               : yarn
* 2024-12-25 01:33:52 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-25 01:33:52 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-25 01:33:52 (9268) [INFO] 
* 2024-12-25 01:33:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-25 01:33:52 (9238) [INFO] 
* 2024-12-25 01:33:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 01:33:52 (9251) [INFO] Determining fastest mirrors
* 2024-12-25 01:33:55 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-25 01:33:55 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-25 01:33:55 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-25 01:33:55 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-25 01:33:55 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-25 01:33:55 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-25 01:33:55 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-25 01:33:56 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-25 01:33:56 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-25 01:33:56 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-25 01:33:56 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-25 01:33:56 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-25 01:33:56 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-25 01:33:56 (9251) [INFO] Trying other mirror.
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-25 01:33:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 01:33:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 01:33:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-25 01:33:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-25 01:33:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-25 01:33:56 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 01:33:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-25 01:33:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-25 01:33:56 (9251) [INFO]         or
* 2024-12-25 01:33:56 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 01:33:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 01:33:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 01:33:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 01:33:56 (9251) [INFO]         compromise:
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-25 01:33:56 (9251) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-25 01:33:56 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-25 01:33:56 (9268) [INFO] 
* 2024-12-25 01:33:56 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-25 01:33:56 (5803) [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-12-25 01:33:56 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-25 01:33:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-25 01:33:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QhoIj_K0fD/ea_profile.json
* 2024-12-25 01:34:01 (484) [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/QhoIj_K0fD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-25 01:34:01 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-26 01:33:24 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-26 01:33:24 (10313) [INFO] Script is up to date.
* 2024-12-26 01:33:25 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-26 01:33:25 (6225) [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-12-26 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-26 01:33:25 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-26 01:33:25 (9238) [INFO] 
* 2024-12-26 01:33:30 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-26 01:33:30 (3970) [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.

* 2024-12-26 01:33:30 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-26 01:33:30 (9238) [INFO] 
* 2024-12-26 01:33:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-26 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-26 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-26 01:33:44 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-26 01:33:44 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-26 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-26 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-26 01:33:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-26 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-26 01:33:44 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-26 01:33:44 (9238) [INFO] 
* 2024-12-26 01:33:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 01:33:44 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-26 01:33:45 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-26 01:33:45 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-26 01:33:45 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-26 01:33:45 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-26 01:33:45 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-26 01:33:45 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-26 01:33:45 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-26 01:33:46 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-26 01:33:46 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-26 01:33:46 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-26 01:33:46 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-26 01:33:46 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-26 01:33:46 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-26 01:33:46 (9251) [INFO] Trying other mirror.
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-26 01:33:46 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 01:33:46 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 01:33:46 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-26 01:33:46 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-26 01:33:46 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-26 01:33:46 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 01:33:46 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-26 01:33:46 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-26 01:33:46 (9251) [INFO]         or
* 2024-12-26 01:33:46 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 01:33:46 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 01:33:46 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 01:33:46 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 01:33:46 (9251) [INFO]         compromise:
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-26 01:33:46 (9251) [INFO] 
* 2024-12-26 01:33:46 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-26 01:33:46 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-26 01:33:47 (9268) [INFO] 
* 2024-12-26 01:33:47 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-26 01:33:47 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-26 01:33:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-26 01:33:47 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-26 01:33:47 (9238) [INFO] 
* 2024-12-26 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 01:33:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-26 01:33:47 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-26 01:33:47 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-26 01:33:47 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-26 01:33:47 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-26 01:33:47 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-26 01:33:47 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-26 01:33:47 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-26 01:33:47 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-26 01:33:47 (9251) [INFO]               : yarn
* 2024-12-26 01:33:47 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-26 01:33:47 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-26 01:33:47 (9268) [INFO] 
* 2024-12-26 01:33:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-26 01:33:47 (9238) [INFO] 
* 2024-12-26 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 01:33:47 (9251) [INFO] Determining fastest mirrors
* 2024-12-26 01:33:49 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-26 01:33:49 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-26 01:33:49 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-26 01:33:49 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-26 01:33:49 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-26 01:33:49 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-26 01:33:49 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-26 01:33:51 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-26 01:33:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-26 01:33:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-26 01:33:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-26 01:33:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-26 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-26 01:33:51 (9251) [INFO] Trying other mirror.
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-26 01:33:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 01:33:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 01:33:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-26 01:33:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-26 01:33:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-26 01:33:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 01:33:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-26 01:33:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-26 01:33:51 (9251) [INFO]         or
* 2024-12-26 01:33:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 01:33:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 01:33:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 01:33:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 01:33:51 (9251) [INFO]         compromise:
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-26 01:33:51 (9251) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-26 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-26 01:33:51 (9268) [INFO] 
* 2024-12-26 01:33:51 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-26 01:33:51 (5803) [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-12-26 01:33:51 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-26 01:33:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-26 01:33:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SyCyEiHVSw/ea_profile.json
* 2024-12-26 01:33:55 (484) [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/SyCyEiHVSw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-26 01:33:55 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-27 01:33:25 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-27 01:33:25 (10313) [INFO] Script is up to date.
* 2024-12-27 01:33:26 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-27 01:33:26 (6225) [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-12-27 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-27 01:33:26 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-27 01:33:26 (9238) [INFO] 
* 2024-12-27 01:33:31 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-27 01:33:31 (3970) [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.

* 2024-12-27 01:33:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-27 01:33:31 (9238) [INFO] 
* 2024-12-27 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-27 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-27 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-27 01:33:39 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-27 01:33:39 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-27 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-27 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-27 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-27 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-27 01:33:39 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-27 01:33:39 (9238) [INFO] 
* 2024-12-27 01:33:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 01:33:39 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-27 01:33:41 (9251) [INFO]  * EA4: 63.247.64.58
* 2024-12-27 01:33:41 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-12-27 01:33:41 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-12-27 01:33:41 (9251) [INFO]  * epel: dl.fedoraproject.org
* 2024-12-27 01:33:41 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-27 01:33:41 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-27 01:33:41 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-27 01:33:42 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-27 01:33:42 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-27 01:33:42 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-27 01:33:42 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-27 01:33:42 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-27 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-27 01:33:42 (9251) [INFO] Trying other mirror.
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-27 01:33:42 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 01:33:42 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 01:33:42 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-27 01:33:42 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-27 01:33:42 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-27 01:33:42 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 01:33:42 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-27 01:33:42 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-27 01:33:42 (9251) [INFO]         or
* 2024-12-27 01:33:42 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 01:33:42 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 01:33:42 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 01:33:42 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 01:33:42 (9251) [INFO]         compromise:
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-27 01:33:42 (9251) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-27 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-27 01:33:42 (9268) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-27 01:33:42 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-27 01:33:42 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-27 01:33:42 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-27 01:33:42 (9238) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 01:33:42 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-27 01:33:42 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-27 01:33:42 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-27 01:33:42 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-27 01:33:42 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-27 01:33:42 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-27 01:33:42 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-27 01:33:42 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-27 01:33:42 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-27 01:33:42 (9251) [INFO]               : yarn
* 2024-12-27 01:33:42 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-27 01:33:42 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-27 01:33:42 (9268) [INFO] 
* 2024-12-27 01:33:42 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-27 01:33:42 (9238) [INFO] 
* 2024-12-27 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 01:33:42 (9251) [INFO] Determining fastest mirrors
* 2024-12-27 01:33:45 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-27 01:33:45 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-27 01:33:45 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-27 01:33:45 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-27 01:33:45 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-27 01:33:45 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-27 01:33:45 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-27 01:33:46 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-27 01:33:46 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-27 01:33:46 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-27 01:33:46 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-27 01:33:46 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-27 01:33:46 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-27 01:33:46 (9251) [INFO] Trying other mirror.
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-27 01:33:46 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 01:33:46 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 01:33:46 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-27 01:33:46 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-27 01:33:46 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-27 01:33:46 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 01:33:46 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-27 01:33:46 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-27 01:33:46 (9251) [INFO]         or
* 2024-12-27 01:33:46 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 01:33:46 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 01:33:46 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 01:33:46 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 01:33:46 (9251) [INFO]         compromise:
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-27 01:33:46 (9251) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-27 01:33:46 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-27 01:33:46 (9268) [INFO] 
* 2024-12-27 01:33:46 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-27 01:33:46 (5803) [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-12-27 01:33:46 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-27 01:33:46 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-27 01:33:47 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hy5YqkMEJK/ea_profile.json
* 2024-12-27 01:33:51 (484) [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/Hy5YqkMEJK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-27 01:33:51 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-28 01:34:05 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-28 01:34:05 (10313) [INFO] Script is up to date.
* 2024-12-28 01:34:07 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-28 01:34:07 (6225) [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-12-28 01:34:10 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-28 01:34:10 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-28 01:34:10 (9238) [INFO] 
* 2024-12-28 01:34:15 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-28 01:34:15 (3970) [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.

* 2024-12-28 01:34:15 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-28 01:34:15 (9238) [INFO] 
* 2024-12-28 01:34:26 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-28 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-28 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-28 01:34:26 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-28 01:34:26 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-28 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-28 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-28 01:34:26 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-28 01:34:26 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-28 01:34:26 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-28 01:34:26 (9238) [INFO] 
* 2024-12-28 01:34:26 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 01:34:26 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-28 01:34:28 (9251) [INFO]  * EA4: 63.247.64.58
* 2024-12-28 01:34:28 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-12-28 01:34:28 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-12-28 01:34:28 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-28 01:34:28 (9251) [INFO]  * remi-php72: rpms.remirepo.net
* 2024-12-28 01:34:28 (9251) [INFO]  * remi-php73: rpms.remirepo.net
* 2024-12-28 01:34:28 (9251) [INFO]  * remi-safe: rpms.remirepo.net
* 2024-12-28 01:34:28 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-28 01:34:28 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-28 01:34:28 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-28 01:34:28 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-28 01:34:28 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-28 01:34:28 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-28 01:34:28 (9251) [INFO] Trying other mirror.
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-28 01:34:28 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 01:34:28 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 01:34:28 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-28 01:34:28 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-28 01:34:28 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-28 01:34:28 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 01:34:28 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-28 01:34:28 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-28 01:34:28 (9251) [INFO]         or
* 2024-12-28 01:34:28 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-28 01:34:28 (9251) [INFO] 
* 2024-12-28 01:34:28 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 01:34:28 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 01:34:28 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 01:34:29 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 01:34:29 (9251) [INFO]         compromise:
* 2024-12-28 01:34:29 (9251) [INFO] 
* 2024-12-28 01:34:29 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-28 01:34:29 (9251) [INFO] 
* 2024-12-28 01:34:29 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-28 01:34:29 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-28 01:34:29 (9268) [INFO] 
* 2024-12-28 01:34:29 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-28 01:34:29 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-28 01:34:29 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-28 01:34:29 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-28 01:34:29 (9238) [INFO] 
* 2024-12-28 01:34:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 01:34:29 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-28 01:34:29 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-28 01:34:29 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-28 01:34:29 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-28 01:34:29 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-28 01:34:29 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-28 01:34:29 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-28 01:34:29 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-28 01:34:29 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-28 01:34:29 (9251) [INFO]               : yarn
* 2024-12-28 01:34:29 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-28 01:34:29 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-28 01:34:29 (9268) [INFO] 
* 2024-12-28 01:34:29 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-28 01:34:29 (9238) [INFO] 
* 2024-12-28 01:34:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 01:34:30 (9251) [INFO] Determining fastest mirrors
* 2024-12-28 01:34:32 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-28 01:34:32 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-28 01:34:32 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-28 01:34:32 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-28 01:34:32 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-28 01:34:32 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-28 01:34:32 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-28 01:34:33 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-28 01:34:33 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-28 01:34:33 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-28 01:34:33 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-28 01:34:33 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-28 01:34:33 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-28 01:34:33 (9251) [INFO] Trying other mirror.
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-28 01:34:33 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 01:34:33 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 01:34:33 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-28 01:34:33 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-28 01:34:33 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-28 01:34:33 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 01:34:33 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-28 01:34:33 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-28 01:34:33 (9251) [INFO]         or
* 2024-12-28 01:34:33 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 01:34:33 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 01:34:33 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 01:34:33 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 01:34:33 (9251) [INFO]         compromise:
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-28 01:34:33 (9251) [INFO] 
* 2024-12-28 01:34:33 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-28 01:34:33 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-28 01:34:34 (9268) [INFO] 
* 2024-12-28 01:34:34 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-28 01:34:34 (5803) [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-12-28 01:34:34 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-28 01:34:34 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-28 01:34:36 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eLXRyoYjN0/ea_profile.json
* 2024-12-28 01:34:40 (484) [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/eLXRyoYjN0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-28 01:34:40 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-29 01:33:59 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-29 01:33:59 (10313) [INFO] Script is up to date.
* 2024-12-29 01:34:00 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-29 01:34:00 (6225) [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-12-29 01:34:00 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-29 01:34:01 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-29 01:34:01 (9238) [INFO] 
* 2024-12-29 01:34:09 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-29 01:34:09 (3970) [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.

* 2024-12-29 01:34:09 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-29 01:34:09 (9238) [INFO] 
* 2024-12-29 01:34:17 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-29 01:34:17 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-29 01:34:17 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-29 01:34:17 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-29 01:34:17 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-29 01:34:17 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-29 01:34:17 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-29 01:34:17 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-29 01:34:17 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-29 01:34:17 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-29 01:34:17 (9238) [INFO] 
* 2024-12-29 01:34:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 01:34:17 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-29 01:34:19 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-29 01:34:19 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-29 01:34:19 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-29 01:34:19 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-29 01:34:19 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2024-12-29 01:34:19 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2024-12-29 01:34:19 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2024-12-29 01:34:20 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-29 01:34:20 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-29 01:34:20 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-29 01:34:20 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-29 01:34:20 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-29 01:34:20 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-29 01:34:20 (9251) [INFO] Trying other mirror.
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-29 01:34:20 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 01:34:20 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 01:34:20 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-29 01:34:20 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-29 01:34:20 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-29 01:34:20 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 01:34:20 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-29 01:34:20 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-29 01:34:20 (9251) [INFO]         or
* 2024-12-29 01:34:20 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 01:34:20 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 01:34:20 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 01:34:20 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 01:34:20 (9251) [INFO]         compromise:
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-29 01:34:20 (9251) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-29 01:34:20 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-29 01:34:20 (9268) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-29 01:34:20 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-29 01:34:20 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-29 01:34:20 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-29 01:34:20 (9238) [INFO] 
* 2024-12-29 01:34:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 01:34:21 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-29 01:34:21 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-29 01:34:21 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-29 01:34:21 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-29 01:34:21 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-29 01:34:21 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-29 01:34:21 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-29 01:34:21 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-29 01:34:21 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-29 01:34:21 (9251) [INFO]               : yarn
* 2024-12-29 01:34:21 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-29 01:34:21 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-29 01:34:21 (9268) [INFO] 
* 2024-12-29 01:34:21 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-29 01:34:21 (9238) [INFO] 
* 2024-12-29 01:34:21 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 01:34:21 (9251) [INFO] Determining fastest mirrors
* 2024-12-29 01:34:24 (9251) [INFO]  * EA4: 63.247.64.58
* 2024-12-29 01:34:24 (9251) [INFO]  * cpanel-addons-production-feed: 63.247.64.58
* 2024-12-29 01:34:24 (9251) [INFO]  * cpanel-plugins: 63.247.64.58
* 2024-12-29 01:34:24 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-29 01:34:24 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-29 01:34:24 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-29 01:34:24 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-29 01:34:24 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-29 01:34:25 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-29 01:34:25 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-29 01:34:25 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-29 01:34:25 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-29 01:34:25 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-29 01:34:25 (9251) [INFO] Trying other mirror.
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-29 01:34:25 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 01:34:25 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 01:34:25 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-29 01:34:25 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-29 01:34:25 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-29 01:34:25 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 01:34:25 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-29 01:34:25 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-29 01:34:25 (9251) [INFO]         or
* 2024-12-29 01:34:25 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 01:34:25 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 01:34:25 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 01:34:25 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 01:34:25 (9251) [INFO]         compromise:
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-29 01:34:25 (9251) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-29 01:34:25 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-29 01:34:25 (9268) [INFO] 
* 2024-12-29 01:34:25 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-29 01:34:25 (5803) [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-12-29 01:34:25 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-29 01:34:25 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-29 01:34:26 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Zstlv1qHnL/ea_profile.json
* 2024-12-29 01:34:28 (484) [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/Zstlv1qHnL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-29 01:34:28 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-30 01:33:25 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-30 01:33:25 (10313) [INFO] Script is up to date.
* 2024-12-30 01:33:26 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-30 01:33:26 (6225) [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-12-30 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-30 01:33:26 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-30 01:33:26 (9238) [INFO] 
* 2024-12-30 01:33:31 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-30 01:33:31 (3970) [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.

* 2024-12-30 01:33:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-30 01:33:31 (9238) [INFO] 
* 2024-12-30 01:33:43 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-30 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-30 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-30 01:33:43 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-30 01:33:43 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-30 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-30 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-30 01:33:43 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-30 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-30 01:33:43 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-30 01:33:43 (9238) [INFO] 
* 2024-12-30 01:33:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 01:33:43 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-30 01:33:44 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-30 01:33:44 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-30 01:33:44 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-30 01:33:44 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-30 01:33:44 (9251) [INFO]  * remi-php72: muug.ca
* 2024-12-30 01:33:44 (9251) [INFO]  * remi-php73: muug.ca
* 2024-12-30 01:33:44 (9251) [INFO]  * remi-safe: muug.ca
* 2024-12-30 01:33:45 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-30 01:33:45 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-30 01:33:45 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-30 01:33:45 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-30 01:33:45 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-30 01:33:45 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-30 01:33:45 (9251) [INFO] Trying other mirror.
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-30 01:33:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 01:33:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 01:33:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-30 01:33:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-30 01:33:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-30 01:33:45 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 01:33:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-30 01:33:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-30 01:33:45 (9251) [INFO]         or
* 2024-12-30 01:33:45 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 01:33:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 01:33:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 01:33:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 01:33:45 (9251) [INFO]         compromise:
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-30 01:33:45 (9251) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-30 01:33:45 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-30 01:33:45 (9268) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-30 01:33:45 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-30 01:33:45 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-30 01:33:45 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-30 01:33:45 (9238) [INFO] 
* 2024-12-30 01:33:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 01:33:45 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-30 01:33:45 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-30 01:33:45 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-30 01:33:45 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-30 01:33:45 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-30 01:33:45 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-30 01:33:45 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-30 01:33:45 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-30 01:33:45 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-30 01:33:45 (9251) [INFO]               : yarn
* 2024-12-30 01:33:46 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-30 01:33:46 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-30 01:33:46 (9268) [INFO] 
* 2024-12-30 01:33:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-30 01:33:46 (9238) [INFO] 
* 2024-12-30 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 01:33:46 (9251) [INFO] Determining fastest mirrors
* 2024-12-30 01:33:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-30 01:33:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-30 01:33:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-30 01:33:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2024-12-30 01:33:50 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-30 01:33:50 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-30 01:33:50 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-30 01:33:50 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-30 01:33:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-30 01:33:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-30 01:33:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-30 01:33:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-30 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-30 01:33:51 (9251) [INFO] Trying other mirror.
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-30 01:33:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 01:33:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 01:33:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-30 01:33:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-30 01:33:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-30 01:33:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 01:33:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-30 01:33:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-30 01:33:51 (9251) [INFO]         or
* 2024-12-30 01:33:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 01:33:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 01:33:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 01:33:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 01:33:51 (9251) [INFO]         compromise:
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-30 01:33:51 (9251) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-30 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-30 01:33:51 (9268) [INFO] 
* 2024-12-30 01:33:51 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-30 01:33:51 (5803) [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-12-30 01:33:51 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-30 01:33:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-30 01:33:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qzew1ZbCCF/ea_profile.json
* 2024-12-30 01:33:55 (484) [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/Qzew1ZbCCF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-30 01:33:55 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-31 01:33:25 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-31 01:33:25 (10313) [INFO] Script is up to date.
* 2024-12-31 01:33:26 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2024-12-31 01:33:26 (6225) [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-12-31 01:33:26 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2024-12-31 01:33:26 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-31 01:33:26 (9238) [INFO] 
* 2024-12-31 01:33:31 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2024-12-31 01:33:31 (3970) [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.

* 2024-12-31 01:33:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-31 01:33:31 (9238) [INFO] 
* 2024-12-31 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2024-12-31 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2024-12-31 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2024-12-31 01:33:39 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-31 01:33:39 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2024-12-31 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2024-12-31 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2024-12-31 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2024-12-31 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2024-12-31 01:33:39 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-31 01:33:39 (9238) [INFO] 
* 2024-12-31 01:33:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 01:33:40 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-31 01:33:41 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-31 01:33:41 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-31 01:33:41 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-31 01:33:41 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-31 01:33:41 (9251) [INFO]  * remi-php72: mirrors.upr.edu
* 2024-12-31 01:33:41 (9251) [INFO]  * remi-php73: mirrors.upr.edu
* 2024-12-31 01:33:41 (9251) [INFO]  * remi-safe: mirrors.upr.edu
* 2024-12-31 01:33:42 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-31 01:33:42 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-31 01:33:42 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-31 01:33:42 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-31 01:33:42 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-31 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-31 01:33:42 (9251) [INFO] Trying other mirror.
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-31 01:33:42 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 01:33:42 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 01:33:42 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-31 01:33:42 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-31 01:33:42 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-31 01:33:42 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 01:33:42 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-31 01:33:42 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-31 01:33:42 (9251) [INFO]         or
* 2024-12-31 01:33:42 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 01:33:42 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 01:33:42 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 01:33:42 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 01:33:42 (9251) [INFO]         compromise:
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-31 01:33:42 (9251) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-31 01:33:42 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-31 01:33:42 (9268) [INFO] 
* 2024-12-31 01:33:42 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-31 01:33:42 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-31 01:33:42 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-31 01:33:42 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-31 01:33:42 (9238) [INFO] 
* 2024-12-31 01:33:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 01:33:43 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2024-12-31 01:33:43 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-31 01:33:43 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-31 01:33:43 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2024-12-31 01:33:43 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-31 01:33:43 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2024-12-31 01:33:43 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2024-12-31 01:33:43 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2024-12-31 01:33:43 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-31 01:33:43 (9251) [INFO]               : yarn
* 2024-12-31 01:33:43 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-31 01:33:43 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2024-12-31 01:33:43 (9268) [INFO] 
* 2024-12-31 01:33:43 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-31 01:33:43 (9238) [INFO] 
* 2024-12-31 01:33:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 01:33:43 (9251) [INFO] Determining fastest mirrors
* 2024-12-31 01:33:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2024-12-31 01:33:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2024-12-31 01:33:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2024-12-31 01:33:46 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2024-12-31 01:33:46 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2024-12-31 01:33:46 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2024-12-31 01:33:46 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2024-12-31 01:33:46 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-31 01:33:47 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2024-12-31 01:33:47 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2024-12-31 01:33:47 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2024-12-31 01:33:47 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2024-12-31 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-31 01:33:47 (9251) [INFO] Trying other mirror.
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2024-12-31 01:33:47 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 01:33:47 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 01:33:47 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-31 01:33:47 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-31 01:33:47 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-31 01:33:47 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 01:33:47 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-31 01:33:47 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2024-12-31 01:33:47 (9251) [INFO]         or
* 2024-12-31 01:33:47 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 01:33:47 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 01:33:47 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 01:33:47 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 01:33:47 (9251) [INFO]         compromise:
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2024-12-31 01:33:47 (9251) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2024-12-31 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-31 01:33:47 (9268) [INFO] 
* 2024-12-31 01:33:47 (9251) [INFO] Is this ok [y/N]: 
* 2024-12-31 01:33:47 (5803) [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-12-31 01:33:47 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2024-12-31 01:33:47 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-31 01:33:48 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b2w53kMXhL/ea_profile.json
* 2024-12-31 01:33:50 (484) [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/b2w53kMXhL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-31 01:33:50 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-01 01:33:31 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-01 01:33:31 (10313) [INFO] Script is up to date.
* 2025-01-01 01:33:32 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-01 01:33:32 (6225) [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.

* 2025-01-01 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-01 01:33:32 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-01 01:33:32 (9238) [INFO] 
* 2025-01-01 01:33:37 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-01 01:33:37 (3970) [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.

* 2025-01-01 01:33:37 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-01 01:33:37 (9238) [INFO] 
* 2025-01-01 01:33:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-01 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-01 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-01 01:33:46 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-01 01:33:46 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-01 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-01 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-01 01:33:46 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-01 01:33:46 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-01 01:33:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-01 01:33:46 (9238) [INFO] 
* 2025-01-01 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 01:33:46 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-01 01:33:47 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-01 01:33:47 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-01 01:33:47 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-01 01:33:47 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-01 01:33:47 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2025-01-01 01:33:47 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2025-01-01 01:33:47 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2025-01-01 01:33:48 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-01 01:33:48 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-01 01:33:48 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-01 01:33:48 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-01 01:33:48 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-01 01:33:48 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-01 01:33:48 (9251) [INFO] Trying other mirror.
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-01 01:33:48 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 01:33:48 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 01:33:48 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-01 01:33:48 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-01 01:33:48 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-01 01:33:48 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 01:33:48 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-01 01:33:48 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-01 01:33:48 (9251) [INFO]         or
* 2025-01-01 01:33:48 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 01:33:48 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 01:33:48 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 01:33:48 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 01:33:48 (9251) [INFO]         compromise:
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-01 01:33:48 (9251) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-01 01:33:48 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-01 01:33:48 (9268) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-01 01:33:48 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-01 01:33:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-01 01:33:48 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-01 01:33:48 (9238) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 01:33:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-01 01:33:48 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-01 01:33:48 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-01 01:33:48 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-01 01:33:48 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-01 01:33:48 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-01 01:33:48 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-01 01:33:48 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-01 01:33:48 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-01 01:33:48 (9251) [INFO]               : yarn
* 2025-01-01 01:33:48 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-01 01:33:48 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-01 01:33:48 (9268) [INFO] 
* 2025-01-01 01:33:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-01 01:33:48 (9238) [INFO] 
* 2025-01-01 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 01:33:49 (9251) [INFO] Determining fastest mirrors
* 2025-01-01 01:33:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-01 01:33:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-01 01:33:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-01 01:33:50 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-01 01:33:50 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-01 01:33:50 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-01 01:33:50 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-01 01:33:51 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-01 01:33:52 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-01 01:33:52 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-01 01:33:52 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-01 01:33:52 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-01 01:33:52 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-01 01:33:52 (9251) [INFO] Trying other mirror.
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-01 01:33:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 01:33:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 01:33:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-01 01:33:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-01 01:33:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-01 01:33:52 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 01:33:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-01 01:33:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-01 01:33:52 (9251) [INFO]         or
* 2025-01-01 01:33:52 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 01:33:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 01:33:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 01:33:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 01:33:52 (9251) [INFO]         compromise:
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-01 01:33:52 (9251) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-01 01:33:52 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-01 01:33:52 (9268) [INFO] 
* 2025-01-01 01:33:52 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-01 01:33:52 (5803) [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/
* 2025-01-01 01:33:52 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-01 01:33:52 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-01 01:33:53 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3umaZlYcDJ/ea_profile.json
* 2025-01-01 01:33:56 (484) [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/3umaZlYcDJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-01 01:33:56 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-02 01:33:31 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-02 01:33:31 (10313) [INFO] Script is up to date.
* 2025-01-02 01:33:32 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-02 01:33:32 (6225) [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.

* 2025-01-02 01:33:32 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-02 01:33:32 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-02 01:33:32 (9238) [INFO] 
* 2025-01-02 01:33:37 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-02 01:33:37 (3970) [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.

* 2025-01-02 01:33:37 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-02 01:33:37 (9238) [INFO] 
* 2025-01-02 01:33:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-02 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-02 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-02 01:33:49 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-02 01:33:49 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-02 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-02 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-02 01:33:49 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-02 01:33:49 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-02 01:33:49 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-02 01:33:49 (9238) [INFO] 
* 2025-01-02 01:33:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 01:33:49 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-02 01:33:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-02 01:33:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-02 01:33:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-02 01:33:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-02 01:33:50 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2025-01-02 01:33:50 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2025-01-02 01:33:50 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2025-01-02 01:33:51 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-02 01:33:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-02 01:33:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-02 01:33:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-02 01:33:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-02 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-02 01:33:51 (9251) [INFO] Trying other mirror.
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-02 01:33:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 01:33:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 01:33:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-02 01:33:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-02 01:33:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-02 01:33:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 01:33:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-02 01:33:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-02 01:33:51 (9251) [INFO]         or
* 2025-01-02 01:33:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 01:33:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 01:33:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 01:33:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 01:33:51 (9251) [INFO]         compromise:
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-02 01:33:51 (9251) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-02 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-02 01:33:51 (9268) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-02 01:33:51 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-02 01:33:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-02 01:33:51 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-02 01:33:51 (9238) [INFO] 
* 2025-01-02 01:33:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 01:33:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-02 01:33:52 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-02 01:33:52 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-02 01:33:52 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-02 01:33:52 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-02 01:33:52 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-02 01:33:52 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-02 01:33:52 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-02 01:33:52 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-02 01:33:52 (9251) [INFO]               : yarn
* 2025-01-02 01:33:52 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-02 01:33:52 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-02 01:33:52 (9268) [INFO] 
* 2025-01-02 01:33:52 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-02 01:33:52 (9238) [INFO] 
* 2025-01-02 01:33:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 01:33:52 (9251) [INFO] Determining fastest mirrors
* 2025-01-02 01:33:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-02 01:33:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-02 01:33:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-02 01:33:54 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-02 01:33:54 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-02 01:33:54 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-02 01:33:54 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-02 01:33:55 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-02 01:33:55 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-02 01:33:55 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-02 01:33:55 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-02 01:33:55 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-02 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-02 01:33:55 (9251) [INFO] Trying other mirror.
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-02 01:33:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 01:33:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 01:33:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-02 01:33:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-02 01:33:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-02 01:33:55 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 01:33:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-02 01:33:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-02 01:33:55 (9251) [INFO]         or
* 2025-01-02 01:33:55 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 01:33:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 01:33:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 01:33:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 01:33:55 (9251) [INFO]         compromise:
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-02 01:33:55 (9251) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-02 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-02 01:33:55 (9268) [INFO] 
* 2025-01-02 01:33:55 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-02 01:33:55 (5803) [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/
* 2025-01-02 01:33:55 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-02 01:33:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-02 01:33:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5aVSQbZ_Sq/ea_profile.json
* 2025-01-02 01:34:00 (484) [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/5aVSQbZ_Sq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-02 01:34:00 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-03 01:33:28 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-03 01:33:28 (10313) [INFO] Script is up to date.
* 2025-01-03 01:33:29 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-03 01:33:29 (6225) [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.

* 2025-01-03 01:33:29 (252) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2025-01-03 01:33:30 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-03 01:33:30 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-03 01:33:30 (9238) [INFO] 
* 2025-01-03 01:33:34 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-03 01:33:34 (3970) [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.

* 2025-01-03 01:33:34 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-03 01:33:34 (9238) [INFO] 
* 2025-01-03 01:33:56 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-03 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-03 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-03 01:33:56 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-03 01:33:56 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-03 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-03 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-03 01:33:56 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-03 01:33:56 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-03 01:33:56 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-03 01:33:56 (9238) [INFO] 
* 2025-01-03 01:33:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 01:33:56 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-03 01:33:58 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-03 01:33:58 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-03 01:33:58 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-03 01:33:58 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-03 01:33:58 (9251) [INFO]  * remi-php72: rpms.remirepo.net
* 2025-01-03 01:33:58 (9251) [INFO]  * remi-php73: rpms.remirepo.net
* 2025-01-03 01:33:58 (9251) [INFO]  * remi-safe: rpms.remirepo.net
* 2025-01-03 01:33:58 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-03 01:33:58 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-03 01:33:58 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-03 01:33:58 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-03 01:33:58 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-03 01:33:58 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-03 01:33:58 (9251) [INFO] Trying other mirror.
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-03 01:33:58 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 01:33:58 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 01:33:58 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-03 01:33:58 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-03 01:33:58 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-03 01:33:58 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 01:33:58 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-03 01:33:58 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-03 01:33:58 (9251) [INFO]         or
* 2025-01-03 01:33:58 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 01:33:58 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 01:33:58 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 01:33:58 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 01:33:58 (9251) [INFO]         compromise:
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-03 01:33:58 (9251) [INFO] 
* 2025-01-03 01:33:58 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-03 01:33:58 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-03 01:33:59 (9268) [INFO] 
* 2025-01-03 01:33:59 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-03 01:33:59 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-03 01:33:59 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-03 01:33:59 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-03 01:33:59 (9238) [INFO] 
* 2025-01-03 01:33:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 01:33:59 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-03 01:33:59 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-03 01:33:59 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-03 01:33:59 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-03 01:33:59 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-03 01:33:59 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-03 01:33:59 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-03 01:33:59 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-03 01:33:59 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-03 01:33:59 (9251) [INFO]               : yarn
* 2025-01-03 01:33:59 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-03 01:33:59 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-03 01:33:59 (9268) [INFO] 
* 2025-01-03 01:33:59 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-03 01:33:59 (9238) [INFO] 
* 2025-01-03 01:33:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 01:33:59 (9251) [INFO] Determining fastest mirrors
* 2025-01-03 01:34:03 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-03 01:34:03 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-03 01:34:03 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-03 01:34:03 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-03 01:34:03 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-03 01:34:03 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-03 01:34:03 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-03 01:34:04 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-03 01:34:04 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-03 01:34:04 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-03 01:34:04 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-03 01:34:04 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-03 01:34:04 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-03 01:34:04 (9251) [INFO] Trying other mirror.
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-03 01:34:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 01:34:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 01:34:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-03 01:34:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-03 01:34:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-03 01:34:04 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 01:34:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-03 01:34:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-03 01:34:04 (9251) [INFO]         or
* 2025-01-03 01:34:04 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 01:34:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 01:34:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 01:34:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 01:34:04 (9251) [INFO]         compromise:
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-03 01:34:04 (9251) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-03 01:34:04 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-03 01:34:04 (9268) [INFO] 
* 2025-01-03 01:34:04 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-03 01:34:04 (5803) [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/
* 2025-01-03 01:34:04 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-03 01:34:04 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-03 01:34:06 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hT934pN3pV/ea_profile.json
* 2025-01-03 01:34:09 (484) [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/hT934pN3pV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-03 01:34:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-04 01:34:18 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-04 01:34:18 (10313) [INFO] Script is up to date.
* 2025-01-04 01:34:19 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-04 01:34:19 (6225) [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.

* 2025-01-04 01:34:19 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-04 01:34:19 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-04 01:34:19 (9238) [INFO] 
* 2025-01-04 01:34:24 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-04 01:34:24 (3970) [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.

* 2025-01-04 01:34:24 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-04 01:34:24 (9238) [INFO] 
* 2025-01-04 01:34:41 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-04 01:34:41 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-04 01:34:41 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-04 01:34:41 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-04 01:34:41 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-04 01:34:41 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-04 01:34:41 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-04 01:34:41 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-04 01:34:41 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-04 01:34:41 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-04 01:34:41 (9238) [INFO] 
* 2025-01-04 01:34:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 01:34:42 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-04 01:34:44 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-04 01:34:44 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-04 01:34:44 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-04 01:34:44 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-04 01:34:44 (9251) [INFO]  * remi-php72: mirrors.upr.edu
* 2025-01-04 01:34:44 (9251) [INFO]  * remi-php73: mirrors.upr.edu
* 2025-01-04 01:34:44 (9251) [INFO]  * remi-safe: mirrors.upr.edu
* 2025-01-04 01:34:45 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-04 01:34:45 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-04 01:34:45 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-04 01:34:45 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-04 01:34:45 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-04 01:34:45 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-04 01:34:45 (9251) [INFO] Trying other mirror.
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-04 01:34:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 01:34:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 01:34:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-04 01:34:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-04 01:34:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-04 01:34:45 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 01:34:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-04 01:34:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-04 01:34:45 (9251) [INFO]         or
* 2025-01-04 01:34:45 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 01:34:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 01:34:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 01:34:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 01:34:45 (9251) [INFO]         compromise:
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-04 01:34:45 (9251) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-04 01:34:45 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-04 01:34:45 (9268) [INFO] 
* 2025-01-04 01:34:45 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-04 01:34:45 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-04 01:34:45 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-04 01:34:45 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-04 01:34:45 (9238) [INFO] 
* 2025-01-04 01:34:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 01:34:46 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-04 01:34:46 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-04 01:34:46 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-04 01:34:46 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-04 01:34:46 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-04 01:34:46 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-04 01:34:46 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-04 01:34:46 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-04 01:34:46 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-04 01:34:46 (9251) [INFO]               : yarn
* 2025-01-04 01:34:46 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-04 01:34:46 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-04 01:34:46 (9268) [INFO] 
* 2025-01-04 01:34:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-04 01:34:46 (9238) [INFO] 
* 2025-01-04 01:34:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 01:34:46 (9251) [INFO] Determining fastest mirrors
* 2025-01-04 01:34:49 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-04 01:34:49 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-04 01:34:49 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-04 01:34:49 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-04 01:34:49 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-04 01:34:49 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-04 01:34:49 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-04 01:34:50 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-04 01:34:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-04 01:34:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-04 01:34:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-04 01:34:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-04 01:34:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-04 01:34:51 (9251) [INFO] Trying other mirror.
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-04 01:34:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 01:34:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 01:34:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-04 01:34:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-04 01:34:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-04 01:34:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 01:34:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-04 01:34:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-04 01:34:51 (9251) [INFO]         or
* 2025-01-04 01:34:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 01:34:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 01:34:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 01:34:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 01:34:51 (9251) [INFO]         compromise:
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-04 01:34:51 (9251) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-04 01:34:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-04 01:34:51 (9268) [INFO] 
* 2025-01-04 01:34:51 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-04 01:34:51 (5803) [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/
* 2025-01-04 01:34:51 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-04 01:34:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-04 01:34:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FtLqLtUt40/ea_profile.json
* 2025-01-04 01:34:55 (484) [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/FtLqLtUt40/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-04 01:34:55 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-05 01:34:02 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-05 01:34:02 (10313) [INFO] Script is up to date.
* 2025-01-05 01:34:03 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-05 01:34:04 (6225) [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.

* 2025-01-05 01:34:07 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-05 01:34:07 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-05 01:34:07 (9238) [INFO] 
* 2025-01-05 01:34:11 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-05 01:34:11 (3970) [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.

* 2025-01-05 01:34:11 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-05 01:34:11 (9238) [INFO] 
* 2025-01-05 01:34:24 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-05 01:34:24 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-05 01:34:24 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-05 01:34:24 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-05 01:34:24 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-05 01:34:24 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-05 01:34:24 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-05 01:34:24 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-05 01:34:24 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-05 01:34:24 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-05 01:34:24 (9238) [INFO] 
* 2025-01-05 01:34:25 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 01:34:25 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-05 01:34:25 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-05 01:34:25 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-05 01:34:25 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-05 01:34:25 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-05 01:34:25 (9251) [INFO]  * remi-php72: mirror.team-cymru.com
* 2025-01-05 01:34:25 (9251) [INFO]  * remi-php73: mirror.team-cymru.com
* 2025-01-05 01:34:25 (9251) [INFO]  * remi-safe: mirror.team-cymru.com
* 2025-01-05 01:34:26 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-05 01:34:26 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-05 01:34:26 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-05 01:34:26 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-05 01:34:26 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-05 01:34:26 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-05 01:34:26 (9251) [INFO] Trying other mirror.
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-05 01:34:26 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 01:34:26 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 01:34:26 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-05 01:34:26 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-05 01:34:26 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-05 01:34:26 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 01:34:26 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-05 01:34:26 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-05 01:34:26 (9251) [INFO]         or
* 2025-01-05 01:34:26 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 01:34:26 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 01:34:26 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 01:34:26 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 01:34:26 (9251) [INFO]         compromise:
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-05 01:34:26 (9251) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-05 01:34:26 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-05 01:34:26 (9268) [INFO] 
* 2025-01-05 01:34:26 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-05 01:34:26 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-05 01:34:26 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-05 01:34:26 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-05 01:34:26 (9238) [INFO] 
* 2025-01-05 01:34:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 01:34:27 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-05 01:34:27 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-05 01:34:27 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-05 01:34:27 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-05 01:34:27 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-05 01:34:27 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-05 01:34:27 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-05 01:34:27 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-05 01:34:27 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-05 01:34:27 (9251) [INFO]               : yarn
* 2025-01-05 01:34:27 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-05 01:34:27 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-05 01:34:27 (9268) [INFO] 
* 2025-01-05 01:34:27 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-05 01:34:27 (9238) [INFO] 
* 2025-01-05 01:34:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 01:34:27 (9251) [INFO] Determining fastest mirrors
* 2025-01-05 01:34:30 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-05 01:34:30 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-05 01:34:30 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-05 01:34:30 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-05 01:34:30 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-05 01:34:30 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-05 01:34:30 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-05 01:34:31 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-05 01:34:31 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-05 01:34:31 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-05 01:34:31 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-05 01:34:31 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-05 01:34:31 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-05 01:34:31 (9251) [INFO] Trying other mirror.
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-05 01:34:31 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 01:34:31 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 01:34:31 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-05 01:34:31 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-05 01:34:31 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-05 01:34:31 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 01:34:31 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-05 01:34:31 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-05 01:34:31 (9251) [INFO]         or
* 2025-01-05 01:34:31 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 01:34:31 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 01:34:31 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 01:34:31 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 01:34:31 (9251) [INFO]         compromise:
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-05 01:34:31 (9251) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-05 01:34:31 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-05 01:34:31 (9268) [INFO] 
* 2025-01-05 01:34:31 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-05 01:34:31 (5803) [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/
* 2025-01-05 01:34:31 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-05 01:34:32 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-05 01:34:33 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8644ggquUT/ea_profile.json
* 2025-01-05 01:34:36 (484) [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/8644ggquUT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-05 01:34:36 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-06 01:33:28 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-06 01:33:28 (10313) [INFO] Script is up to date.
* 2025-01-06 01:33:29 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-06 01:33:29 (6225) [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.

* 2025-01-06 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-06 01:33:29 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-06 01:33:29 (9238) [INFO] 
* 2025-01-06 01:33:33 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-06 01:33:33 (3970) [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.

* 2025-01-06 01:33:33 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-06 01:33:33 (9238) [INFO] 
* 2025-01-06 01:33:43 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-06 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-06 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-06 01:33:43 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-06 01:33:43 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-06 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-06 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-06 01:33:43 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-06 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-06 01:33:43 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-06 01:33:43 (9238) [INFO] 
* 2025-01-06 01:33:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 01:33:43 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-06 01:33:44 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-06 01:33:44 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-06 01:33:44 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-06 01:33:44 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-06 01:33:44 (9251) [INFO]  * remi-php72: muug.ca
* 2025-01-06 01:33:44 (9251) [INFO]  * remi-php73: muug.ca
* 2025-01-06 01:33:44 (9251) [INFO]  * remi-safe: muug.ca
* 2025-01-06 01:33:45 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-06 01:33:45 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-06 01:33:45 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-06 01:33:45 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-06 01:33:45 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-06 01:33:45 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-06 01:33:45 (9251) [INFO] Trying other mirror.
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-06 01:33:45 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 01:33:45 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 01:33:45 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-06 01:33:45 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-06 01:33:45 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-06 01:33:45 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 01:33:45 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-06 01:33:45 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-06 01:33:45 (9251) [INFO]         or
* 2025-01-06 01:33:45 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 01:33:45 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 01:33:45 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 01:33:45 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 01:33:45 (9251) [INFO]         compromise:
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-06 01:33:45 (9251) [INFO] 
* 2025-01-06 01:33:45 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-06 01:33:45 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-06 01:33:46 (9268) [INFO] 
* 2025-01-06 01:33:46 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-06 01:33:46 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-06 01:33:46 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-06 01:33:46 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-06 01:33:46 (9238) [INFO] 
* 2025-01-06 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 01:33:46 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-06 01:33:46 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-06 01:33:46 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-06 01:33:46 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-06 01:33:46 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-06 01:33:46 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-06 01:33:46 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-06 01:33:46 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-06 01:33:46 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-06 01:33:46 (9251) [INFO]               : yarn
* 2025-01-06 01:33:46 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-06 01:33:46 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-06 01:33:46 (9268) [INFO] 
* 2025-01-06 01:33:46 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-06 01:33:46 (9238) [INFO] 
* 2025-01-06 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 01:33:46 (9251) [INFO] Determining fastest mirrors
* 2025-01-06 01:33:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-06 01:33:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-06 01:33:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-06 01:33:51 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-06 01:33:51 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-06 01:33:51 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-06 01:33:51 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-06 01:33:52 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-06 01:33:53 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-06 01:33:53 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-06 01:33:53 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-06 01:33:53 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-06 01:33:53 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-06 01:33:53 (9251) [INFO] Trying other mirror.
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-06 01:33:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 01:33:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 01:33:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-06 01:33:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-06 01:33:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-06 01:33:53 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 01:33:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-06 01:33:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-06 01:33:53 (9251) [INFO]         or
* 2025-01-06 01:33:53 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 01:33:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 01:33:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 01:33:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 01:33:53 (9251) [INFO]         compromise:
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-06 01:33:53 (9251) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-06 01:33:53 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-06 01:33:53 (9268) [INFO] 
* 2025-01-06 01:33:53 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-06 01:33:53 (5803) [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/
* 2025-01-06 01:33:53 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-06 01:33:53 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-06 01:33:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QgDmP54y17/ea_profile.json
* 2025-01-06 01:33:57 (484) [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/QgDmP54y17/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-06 01:33:57 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-07 01:33:24 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-07 01:33:24 (10313) [INFO] Script is up to date.
* 2025-01-07 01:33:25 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-07 01:33:25 (6225) [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.

* 2025-01-07 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-07 01:33:25 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-07 01:33:25 (9238) [INFO] 
* 2025-01-07 01:33:30 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-07 01:33:30 (3970) [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.

* 2025-01-07 01:33:30 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-07 01:33:30 (9238) [INFO] 
* 2025-01-07 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-07 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-07 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-07 01:33:39 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-07 01:33:39 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-07 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-07 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-07 01:33:39 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-07 01:33:39 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-07 01:33:39 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-07 01:33:39 (9238) [INFO] 
* 2025-01-07 01:33:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 01:33:39 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-07 01:33:40 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-07 01:33:40 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-07 01:33:40 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-07 01:33:40 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-07 01:33:40 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2025-01-07 01:33:40 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2025-01-07 01:33:40 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2025-01-07 01:33:40 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-07 01:33:41 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-07 01:33:41 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-07 01:33:41 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-07 01:33:41 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-07 01:33:41 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-07 01:33:41 (9251) [INFO] Trying other mirror.
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-07 01:33:41 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 01:33:41 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 01:33:41 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-07 01:33:41 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-07 01:33:41 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-07 01:33:41 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 01:33:41 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-07 01:33:41 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-07 01:33:41 (9251) [INFO]         or
* 2025-01-07 01:33:41 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 01:33:41 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 01:33:41 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 01:33:41 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 01:33:41 (9251) [INFO]         compromise:
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-07 01:33:41 (9251) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-07 01:33:41 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-07 01:33:41 (9268) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-07 01:33:41 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-07 01:33:41 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-07 01:33:41 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-07 01:33:41 (9238) [INFO] 
* 2025-01-07 01:33:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 01:33:41 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-07 01:33:41 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-07 01:33:41 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-07 01:33:41 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-07 01:33:41 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-07 01:33:41 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-07 01:33:41 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-07 01:33:41 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-07 01:33:41 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-07 01:33:41 (9251) [INFO]               : yarn
* 2025-01-07 01:33:41 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-07 01:33:41 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-07 01:33:41 (9268) [INFO] 
* 2025-01-07 01:33:41 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-07 01:33:41 (9238) [INFO] 
* 2025-01-07 01:33:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 01:33:42 (9251) [INFO] Determining fastest mirrors
* 2025-01-07 01:33:43 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-07 01:33:43 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-07 01:33:43 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-07 01:33:43 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-07 01:33:43 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-07 01:33:43 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-07 01:33:43 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-07 01:33:44 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-07 01:33:44 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-07 01:33:44 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-07 01:33:44 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-07 01:33:44 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-07 01:33:44 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-07 01:33:44 (9251) [INFO] Trying other mirror.
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-07 01:33:44 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 01:33:44 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 01:33:44 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-07 01:33:44 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-07 01:33:44 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-07 01:33:44 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 01:33:44 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-07 01:33:44 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-07 01:33:44 (9251) [INFO]         or
* 2025-01-07 01:33:44 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 01:33:44 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 01:33:44 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 01:33:44 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 01:33:44 (9251) [INFO]         compromise:
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-07 01:33:44 (9251) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-07 01:33:44 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-07 01:33:44 (9268) [INFO] 
* 2025-01-07 01:33:44 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-07 01:33:44 (5803) [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/
* 2025-01-07 01:33:44 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-07 01:33:44 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-07 01:33:46 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uTTQ_mCT3U/ea_profile.json
* 2025-01-07 01:33:50 (484) [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/uTTQ_mCT3U/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-07 01:33:50 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-08 01:33:28 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-08 01:33:28 (10313) [INFO] Script is up to date.
* 2025-01-08 01:33:29 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-08 01:33:29 (6225) [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.

* 2025-01-08 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-08 01:33:29 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-08 01:33:29 (9238) [INFO] 
* 2025-01-08 01:33:35 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-08 01:33:35 (3970) [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.

* 2025-01-08 01:33:35 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-08 01:33:35 (9238) [INFO] 
* 2025-01-08 01:33:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-08 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-08 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-08 01:33:47 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-08 01:33:47 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-08 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-08 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-08 01:33:47 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-08 01:33:47 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-08 01:33:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-08 01:33:47 (9238) [INFO] 
* 2025-01-08 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 01:33:47 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-08 01:33:49 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-08 01:33:49 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-08 01:33:49 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-08 01:33:49 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-08 01:33:49 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2025-01-08 01:33:49 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2025-01-08 01:33:49 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2025-01-08 01:33:49 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-08 01:33:50 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-08 01:33:50 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-08 01:33:50 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-08 01:33:50 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-08 01:33:50 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-08 01:33:50 (9251) [INFO] Trying other mirror.
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-08 01:33:50 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 01:33:50 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 01:33:50 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-08 01:33:50 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-08 01:33:50 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-08 01:33:50 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 01:33:50 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-08 01:33:50 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-08 01:33:50 (9251) [INFO]         or
* 2025-01-08 01:33:50 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 01:33:50 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 01:33:50 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 01:33:50 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 01:33:50 (9251) [INFO]         compromise:
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-08 01:33:50 (9251) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-08 01:33:50 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-08 01:33:50 (9268) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-08 01:33:50 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-08 01:33:50 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-08 01:33:50 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-08 01:33:50 (9238) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 01:33:50 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-08 01:33:50 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-08 01:33:50 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-08 01:33:50 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-08 01:33:50 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-08 01:33:50 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-08 01:33:50 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-08 01:33:50 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-08 01:33:50 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-08 01:33:50 (9251) [INFO]               : yarn
* 2025-01-08 01:33:50 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-08 01:33:50 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-08 01:33:50 (9268) [INFO] 
* 2025-01-08 01:33:50 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-08 01:33:50 (9238) [INFO] 
* 2025-01-08 01:33:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 01:33:51 (9251) [INFO] Determining fastest mirrors
* 2025-01-08 01:33:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-08 01:33:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-08 01:33:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-08 01:33:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-08 01:33:54 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-08 01:33:54 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-08 01:33:54 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-08 01:33:55 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-08 01:33:55 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-08 01:33:55 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-08 01:33:55 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-08 01:33:55 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-08 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-08 01:33:55 (9251) [INFO] Trying other mirror.
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-08 01:33:55 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 01:33:55 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 01:33:55 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-08 01:33:55 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-08 01:33:55 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-08 01:33:55 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 01:33:55 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-08 01:33:55 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-08 01:33:55 (9251) [INFO]         or
* 2025-01-08 01:33:55 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 01:33:55 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 01:33:55 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 01:33:55 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 01:33:55 (9251) [INFO]         compromise:
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-08 01:33:55 (9251) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-08 01:33:55 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-08 01:33:55 (9268) [INFO] 
* 2025-01-08 01:33:55 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-08 01:33:55 (5803) [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/
* 2025-01-08 01:33:55 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-08 01:33:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-08 01:33:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/O9JtpBLEmB/ea_profile.json
* 2025-01-08 01:33:58 (484) [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/O9JtpBLEmB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-08 01:33:58 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-09 01:33:24 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-09 01:33:24 (10313) [INFO] Script is up to date.
* 2025-01-09 01:33:25 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-09 01:33:25 (6225) [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.

* 2025-01-09 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-09 01:33:25 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-09 01:33:25 (9238) [INFO] 
* 2025-01-09 01:33:31 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-09 01:33:31 (3970) [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.

* 2025-01-09 01:33:31 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-09 01:33:31 (9238) [INFO] 
* 2025-01-09 01:33:45 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-09 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-09 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-09 01:33:45 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-09 01:33:45 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-09 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-09 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-09 01:33:45 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-09 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-09 01:33:45 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-09 01:33:45 (9238) [INFO] 
* 2025-01-09 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 01:33:46 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-09 01:33:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-09 01:33:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-09 01:33:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-09 01:33:46 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-09 01:33:46 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2025-01-09 01:33:46 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2025-01-09 01:33:46 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2025-01-09 01:33:47 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-09 01:33:47 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-09 01:33:47 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-09 01:33:47 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-09 01:33:47 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-09 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-09 01:33:47 (9251) [INFO] Trying other mirror.
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-09 01:33:47 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 01:33:47 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 01:33:47 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-09 01:33:47 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-09 01:33:47 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-09 01:33:47 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 01:33:47 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-09 01:33:47 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-09 01:33:47 (9251) [INFO]         or
* 2025-01-09 01:33:47 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 01:33:47 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 01:33:47 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 01:33:47 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 01:33:47 (9251) [INFO]         compromise:
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-09 01:33:47 (9251) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-09 01:33:47 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-09 01:33:47 (9268) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-09 01:33:47 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-09 01:33:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-09 01:33:47 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-09 01:33:47 (9238) [INFO] 
* 2025-01-09 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 01:33:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-09 01:33:48 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-09 01:33:48 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-09 01:33:48 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-09 01:33:48 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-09 01:33:48 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-09 01:33:48 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-09 01:33:48 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-09 01:33:48 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-09 01:33:48 (9251) [INFO]               : yarn
* 2025-01-09 01:33:48 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-09 01:33:48 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-09 01:33:48 (9268) [INFO] 
* 2025-01-09 01:33:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-09 01:33:48 (9238) [INFO] 
* 2025-01-09 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 01:33:48 (9251) [INFO] Determining fastest mirrors
* 2025-01-09 01:33:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-09 01:33:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-09 01:33:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-09 01:33:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-09 01:33:50 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-09 01:33:50 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-09 01:33:50 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-09 01:33:51 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-09 01:33:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-09 01:33:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-09 01:33:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-09 01:33:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-09 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-09 01:33:51 (9251) [INFO] Trying other mirror.
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-09 01:33:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 01:33:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 01:33:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-09 01:33:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-09 01:33:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-09 01:33:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 01:33:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-09 01:33:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-09 01:33:51 (9251) [INFO]         or
* 2025-01-09 01:33:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 01:33:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 01:33:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 01:33:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 01:33:51 (9251) [INFO]         compromise:
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-09 01:33:51 (9251) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-09 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-09 01:33:51 (9268) [INFO] 
* 2025-01-09 01:33:51 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-09 01:33:51 (5803) [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/
* 2025-01-09 01:33:51 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-09 01:33:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-09 01:33:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5khf3qWIui/ea_profile.json
* 2025-01-09 01:33:54 (484) [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/5khf3qWIui/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-09 01:33:54 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-10 01:33:26 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-10 01:33:26 (10313) [INFO] Script is up to date.
* 2025-01-10 01:33:27 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-10 01:33:27 (6225) [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.

* 2025-01-10 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-10 01:33:27 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-10 01:33:27 (9238) [INFO] 
* 2025-01-10 01:33:32 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-10 01:33:32 (3970) [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.

* 2025-01-10 01:33:32 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-10 01:33:32 (9238) [INFO] 
* 2025-01-10 01:33:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-10 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-10 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-10 01:33:44 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-10 01:33:44 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-10 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-10 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-10 01:33:44 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-10 01:33:44 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-10 01:33:44 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-10 01:33:44 (9238) [INFO] 
* 2025-01-10 01:33:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 01:33:44 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-10 01:33:45 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-10 01:33:45 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-10 01:33:45 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-10 01:33:45 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-10 01:33:45 (9251) [INFO]  * remi-php72: mirror.netweaver.uk
* 2025-01-10 01:33:45 (9251) [INFO]  * remi-php73: mirror.netweaver.uk
* 2025-01-10 01:33:45 (9251) [INFO]  * remi-safe: mirror.netweaver.uk
* 2025-01-10 01:33:46 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-10 01:33:46 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-10 01:33:46 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-10 01:33:46 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-10 01:33:46 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-10 01:33:46 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-10 01:33:46 (9251) [INFO] Trying other mirror.
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-10 01:33:46 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 01:33:46 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 01:33:46 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-10 01:33:46 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-10 01:33:46 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-10 01:33:46 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 01:33:46 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-10 01:33:46 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-10 01:33:46 (9251) [INFO]         or
* 2025-01-10 01:33:46 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 01:33:46 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 01:33:46 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 01:33:46 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 01:33:46 (9251) [INFO]         compromise:
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-10 01:33:46 (9251) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-10 01:33:46 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-10 01:33:46 (9268) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-10 01:33:46 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-10 01:33:46 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-10 01:33:46 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-10 01:33:46 (9238) [INFO] 
* 2025-01-10 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 01:33:46 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-10 01:33:46 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-10 01:33:46 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-10 01:33:46 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-10 01:33:46 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-10 01:33:46 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-10 01:33:46 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-10 01:33:46 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-10 01:33:46 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-10 01:33:46 (9251) [INFO]               : yarn
* 2025-01-10 01:33:46 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-10 01:33:46 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-10 01:33:47 (9268) [INFO] 
* 2025-01-10 01:33:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-10 01:33:47 (9238) [INFO] 
* 2025-01-10 01:33:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 01:33:47 (9251) [INFO] Determining fastest mirrors
* 2025-01-10 01:33:49 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-10 01:33:49 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-10 01:33:49 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-10 01:33:49 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-10 01:33:49 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-10 01:33:49 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-10 01:33:49 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-10 01:33:50 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-10 01:33:50 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-10 01:33:50 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-10 01:33:50 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-10 01:33:50 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-10 01:33:50 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-10 01:33:50 (9251) [INFO] Trying other mirror.
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-10 01:33:50 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 01:33:50 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 01:33:50 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-10 01:33:50 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-10 01:33:50 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-10 01:33:50 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 01:33:50 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-10 01:33:50 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-10 01:33:50 (9251) [INFO]         or
* 2025-01-10 01:33:50 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 01:33:50 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 01:33:50 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 01:33:50 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 01:33:50 (9251) [INFO]         compromise:
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-10 01:33:50 (9251) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-10 01:33:50 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-10 01:33:50 (9268) [INFO] 
* 2025-01-10 01:33:50 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-10 01:33:50 (5803) [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/
* 2025-01-10 01:33:50 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-10 01:33:50 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-10 01:33:51 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p5F1ay9LGI/ea_profile.json
* 2025-01-10 01:33:54 (484) [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/p5F1ay9LGI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-10 01:33:54 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-11 01:34:12 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-11 01:34:12 (10313) [INFO] Script is up to date.
* 2025-01-11 01:34:14 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-11 01:34:14 (6225) [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.

* 2025-01-11 01:34:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-11 01:34:14 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-11 01:34:14 (9238) [INFO] 
* 2025-01-11 01:34:19 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-11 01:34:19 (3970) [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.

* 2025-01-11 01:34:19 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-11 01:34:19 (9238) [INFO] 
* 2025-01-11 01:34:28 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-11 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-11 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-11 01:34:28 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-11 01:34:28 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-11 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-11 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-11 01:34:28 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-11 01:34:28 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-11 01:34:28 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-11 01:34:28 (9238) [INFO] 
* 2025-01-11 01:34:28 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 01:34:28 (9251) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 603686.
* 2025-01-11 01:34:28 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2025-01-11 01:34:28 (9251) [INFO]   The other application is: yum
* 2025-01-11 01:34:28 (9251) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2025-01-11 01:34:28 (9251) [INFO]     Started: Sat Jan 11 01:34:23 2025 - 00:05 ago
* 2025-01-11 01:34:28 (9251) [INFO]     State  : Sleeping, pid: 603686
* 2025-01-11 01:34:30 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2025-01-11 01:34:30 (9251) [INFO]   The other application is: yum
* 2025-01-11 01:34:30 (9251) [INFO]     Memory :  40 M RSS (333 MB VSZ)
* 2025-01-11 01:34:30 (9251) [INFO]     Started: Sat Jan 11 01:34:23 2025 - 00:07 ago
* 2025-01-11 01:34:30 (9251) [INFO]     State  : Sleeping, pid: 603686
* 2025-01-11 01:34:32 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-11 01:34:34 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-11 01:34:34 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-11 01:34:34 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-11 01:34:34 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-11 01:34:34 (9251) [INFO]  * remi-php72: mirror.pit.teraswitch.com
* 2025-01-11 01:34:34 (9251) [INFO]  * remi-php73: mirror.pit.teraswitch.com
* 2025-01-11 01:34:34 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-11 01:34:35 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-11 01:34:35 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-11 01:34:35 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-11 01:34:35 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-11 01:34:35 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-11 01:34:35 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-11 01:34:35 (9251) [INFO] Trying other mirror.
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-11 01:34:35 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 01:34:35 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 01:34:35 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-11 01:34:35 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-11 01:34:35 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-11 01:34:35 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 01:34:35 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-11 01:34:35 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-11 01:34:35 (9251) [INFO]         or
* 2025-01-11 01:34:35 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 01:34:35 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 01:34:35 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 01:34:35 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 01:34:35 (9251) [INFO]         compromise:
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-11 01:34:35 (9251) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-11 01:34:35 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-11 01:34:35 (9268) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-11 01:34:35 (5793) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 603686.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Sat Jan 11 01:34:23 2025 - 00:05 ago
    State  : Sleeping, pid: 603686
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (333 MB VSZ)
    Started: Sat Jan 11 01:34:23 2025 - 00:07 ago
    State  : Sleeping, pid: 603686
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-11 01:34:35 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-11 01:34:35 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-11 01:34:35 (9238) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 01:34:35 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-11 01:34:35 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-11 01:34:35 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-11 01:34:35 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-11 01:34:35 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-11 01:34:35 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-11 01:34:35 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-11 01:34:35 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-11 01:34:35 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-11 01:34:35 (9251) [INFO]               : yarn
* 2025-01-11 01:34:35 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-11 01:34:35 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-11 01:34:35 (9268) [INFO] 
* 2025-01-11 01:34:35 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-11 01:34:35 (9238) [INFO] 
* 2025-01-11 01:34:35 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 01:34:36 (9251) [INFO] Determining fastest mirrors
* 2025-01-11 01:34:38 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-11 01:34:38 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-11 01:34:38 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-11 01:34:38 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-11 01:34:38 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-11 01:34:38 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-11 01:34:38 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-11 01:34:39 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-11 01:34:39 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-11 01:34:39 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-11 01:34:39 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-11 01:34:39 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-11 01:34:39 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-11 01:34:39 (9251) [INFO] Trying other mirror.
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-11 01:34:39 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 01:34:39 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 01:34:39 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-11 01:34:39 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-11 01:34:39 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-11 01:34:39 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 01:34:39 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-11 01:34:39 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-11 01:34:39 (9251) [INFO]         or
* 2025-01-11 01:34:39 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 01:34:39 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 01:34:39 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 01:34:39 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 01:34:39 (9251) [INFO]         compromise:
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-11 01:34:39 (9251) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-11 01:34:39 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-11 01:34:39 (9268) [INFO] 
* 2025-01-11 01:34:39 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-11 01:34:39 (5803) [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/
* 2025-01-11 01:34:39 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-11 01:34:39 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-11 01:34:40 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mF8czqJ2pz/ea_profile.json
* 2025-01-11 01:34:43 (484) [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/mF8czqJ2pz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-11 01:34:43 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-12 01:34:01 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-12 01:34:01 (10313) [INFO] Script is up to date.
* 2025-01-12 01:34:02 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-12 01:34:02 (6225) [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.

* 2025-01-12 01:34:02 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-12 01:34:02 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-12 01:34:02 (9238) [INFO] 
* 2025-01-12 01:34:07 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-12 01:34:07 (3970) [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.

* 2025-01-12 01:34:07 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-12 01:34:07 (9238) [INFO] 
* 2025-01-12 01:34:16 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-12 01:34:16 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-12 01:34:16 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-12 01:34:16 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-12 01:34:16 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-12 01:34:16 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-12 01:34:16 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-12 01:34:16 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-12 01:34:16 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-12 01:34:16 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-12 01:34:16 (9238) [INFO] 
* 2025-01-12 01:34:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 01:34:17 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-12 01:34:18 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-12 01:34:18 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-12 01:34:18 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-12 01:34:18 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-12 01:34:18 (9251) [INFO]  * remi-php72: mirror.pit.teraswitch.com
* 2025-01-12 01:34:18 (9251) [INFO]  * remi-php73: mirror.pit.teraswitch.com
* 2025-01-12 01:34:18 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-12 01:34:19 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-12 01:34:19 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-12 01:34:19 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-12 01:34:19 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-12 01:34:19 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-12 01:34:19 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-12 01:34:19 (9251) [INFO] Trying other mirror.
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-12 01:34:19 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 01:34:19 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 01:34:19 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-12 01:34:19 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-12 01:34:19 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-12 01:34:19 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 01:34:19 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-12 01:34:19 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-12 01:34:19 (9251) [INFO]         or
* 2025-01-12 01:34:19 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 01:34:19 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 01:34:19 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 01:34:19 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 01:34:19 (9251) [INFO]         compromise:
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-12 01:34:19 (9251) [INFO] 
* 2025-01-12 01:34:19 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-12 01:34:19 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-12 01:34:20 (9268) [INFO] 
* 2025-01-12 01:34:20 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-12 01:34:20 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-12 01:34:20 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-12 01:34:20 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-12 01:34:20 (9238) [INFO] 
* 2025-01-12 01:34:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 01:34:20 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-12 01:34:20 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-12 01:34:20 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-12 01:34:20 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-12 01:34:20 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-12 01:34:20 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-12 01:34:20 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-12 01:34:20 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-12 01:34:20 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-12 01:34:20 (9251) [INFO]               : yarn
* 2025-01-12 01:34:20 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-12 01:34:20 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-12 01:34:20 (9268) [INFO] 
* 2025-01-12 01:34:20 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-12 01:34:20 (9238) [INFO] 
* 2025-01-12 01:34:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 01:34:20 (9251) [INFO] Determining fastest mirrors
* 2025-01-12 01:34:22 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-12 01:34:22 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-12 01:34:22 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-12 01:34:22 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-12 01:34:22 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-12 01:34:22 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-12 01:34:22 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-12 01:34:23 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-12 01:34:23 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-12 01:34:23 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-12 01:34:23 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-12 01:34:23 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-12 01:34:23 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-12 01:34:23 (9251) [INFO] Trying other mirror.
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-12 01:34:23 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 01:34:23 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 01:34:23 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-12 01:34:23 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-12 01:34:23 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-12 01:34:23 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 01:34:23 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-12 01:34:23 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-12 01:34:23 (9251) [INFO]         or
* 2025-01-12 01:34:23 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 01:34:23 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 01:34:23 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 01:34:23 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 01:34:23 (9251) [INFO]         compromise:
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-12 01:34:23 (9251) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-12 01:34:23 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-12 01:34:23 (9268) [INFO] 
* 2025-01-12 01:34:23 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-12 01:34:23 (5803) [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/
* 2025-01-12 01:34:23 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-12 01:34:23 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-12 01:34:25 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_6_7yhzUOp/ea_profile.json
* 2025-01-12 01:34:28 (484) [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/_6_7yhzUOp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-12 01:34:28 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-13 01:33:28 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-13 01:33:28 (10313) [INFO] Script is up to date.
* 2025-01-13 01:33:29 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-13 01:33:29 (6225) [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.

* 2025-01-13 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-13 01:33:29 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-13 01:33:29 (9238) [INFO] 
* 2025-01-13 01:33:34 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-13 01:33:34 (3970) [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.

* 2025-01-13 01:33:34 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-13 01:33:34 (9238) [INFO] 
* 2025-01-13 01:33:48 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-13 01:33:48 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-13 01:33:48 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-13 01:33:48 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-13 01:33:48 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-13 01:33:48 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-13 01:33:48 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-13 01:33:48 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-13 01:33:48 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-13 01:33:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-13 01:33:48 (9238) [INFO] 
* 2025-01-13 01:33:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 01:33:49 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-13 01:33:50 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-13 01:33:50 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-13 01:33:50 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-13 01:33:50 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-13 01:33:50 (9251) [INFO]  * remi-php72: mirror.oxilion.nl
* 2025-01-13 01:33:50 (9251) [INFO]  * remi-php73: mirror.oxilion.nl
* 2025-01-13 01:33:50 (9251) [INFO]  * remi-safe: mirror.oxilion.nl
* 2025-01-13 01:33:50 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-13 01:33:51 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-13 01:33:51 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-13 01:33:51 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-13 01:33:51 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-13 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-13 01:33:51 (9251) [INFO] Trying other mirror.
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-13 01:33:51 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 01:33:51 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 01:33:51 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-13 01:33:51 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-13 01:33:51 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-13 01:33:51 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 01:33:51 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-13 01:33:51 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-13 01:33:51 (9251) [INFO]         or
* 2025-01-13 01:33:51 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 01:33:51 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 01:33:51 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 01:33:51 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 01:33:51 (9251) [INFO]         compromise:
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-13 01:33:51 (9251) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-13 01:33:51 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-13 01:33:51 (9268) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-13 01:33:51 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-13 01:33:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-13 01:33:51 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-13 01:33:51 (9238) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 01:33:51 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-13 01:33:51 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-13 01:33:51 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-13 01:33:51 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-13 01:33:51 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-13 01:33:51 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-13 01:33:51 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-13 01:33:51 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-13 01:33:51 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-13 01:33:51 (9251) [INFO]               : yarn
* 2025-01-13 01:33:51 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-13 01:33:51 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-13 01:33:51 (9268) [INFO] 
* 2025-01-13 01:33:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-13 01:33:51 (9238) [INFO] 
* 2025-01-13 01:33:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 01:33:52 (9251) [INFO] Determining fastest mirrors
* 2025-01-13 01:33:54 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-13 01:33:54 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-13 01:33:54 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-13 01:33:54 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-13 01:33:54 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-13 01:33:54 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-13 01:33:54 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-13 01:33:56 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-13 01:33:56 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-13 01:33:56 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-13 01:33:56 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-13 01:33:56 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-13 01:33:56 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-13 01:33:56 (9251) [INFO] Trying other mirror.
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-13 01:33:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 01:33:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 01:33:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-13 01:33:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-13 01:33:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-13 01:33:56 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 01:33:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-13 01:33:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-13 01:33:56 (9251) [INFO]         or
* 2025-01-13 01:33:56 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 01:33:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 01:33:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 01:33:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 01:33:56 (9251) [INFO]         compromise:
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-13 01:33:56 (9251) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-13 01:33:56 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-13 01:33:56 (9268) [INFO] 
* 2025-01-13 01:33:56 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-13 01:33:56 (5803) [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/
* 2025-01-13 01:33:56 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-13 01:33:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-13 01:33:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/98udSo4VNE/ea_profile.json
* 2025-01-13 01:34:01 (484) [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/98udSo4VNE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-13 01:34:01 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-14 01:33:25 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-14 01:33:25 (10313) [INFO] Script is up to date.
* 2025-01-14 01:33:27 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-14 01:33:27 (6225) [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.

* 2025-01-14 01:33:27 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-14 01:33:27 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-14 01:33:27 (9238) [INFO] 
* 2025-01-14 01:33:33 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-14 01:33:33 (3970) [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.

* 2025-01-14 01:33:33 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-14 01:33:33 (9238) [INFO] 
* 2025-01-14 01:33:45 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-14 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-14 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-14 01:33:45 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-14 01:33:45 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-14 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-14 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-14 01:33:45 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-14 01:33:45 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-14 01:33:45 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-14 01:33:45 (9238) [INFO] 
* 2025-01-14 01:33:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 01:33:46 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-14 01:33:47 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-14 01:33:47 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-14 01:33:47 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-14 01:33:47 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-14 01:33:47 (9251) [INFO]  * remi-php72: mirror.pit.teraswitch.com
* 2025-01-14 01:33:47 (9251) [INFO]  * remi-php73: mirror.pit.teraswitch.com
* 2025-01-14 01:33:47 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-14 01:33:48 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-14 01:33:48 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-14 01:33:48 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-14 01:33:48 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-14 01:33:48 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-14 01:33:48 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-14 01:33:48 (9251) [INFO] Trying other mirror.
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-14 01:33:48 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 01:33:48 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 01:33:48 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-14 01:33:48 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-14 01:33:48 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-14 01:33:48 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 01:33:48 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-14 01:33:48 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-14 01:33:48 (9251) [INFO]         or
* 2025-01-14 01:33:48 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 01:33:48 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 01:33:48 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 01:33:48 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 01:33:48 (9251) [INFO]         compromise:
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-14 01:33:48 (9251) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-14 01:33:48 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-14 01:33:48 (9268) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-14 01:33:48 (5793) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-14 01:33:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-14 01:33:48 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-14 01:33:48 (9238) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 01:33:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-14 01:33:48 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-14 01:33:48 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-14 01:33:48 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-14 01:33:48 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-14 01:33:48 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-14 01:33:48 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-14 01:33:48 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-14 01:33:48 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-14 01:33:48 (9251) [INFO]               : yarn
* 2025-01-14 01:33:48 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-14 01:33:48 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-14 01:33:48 (9268) [INFO] 
* 2025-01-14 01:33:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-14 01:33:48 (9238) [INFO] 
* 2025-01-14 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 01:33:49 (9251) [INFO] Determining fastest mirrors
* 2025-01-14 01:33:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-14 01:33:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-14 01:33:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-14 01:33:51 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-14 01:33:51 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-14 01:33:51 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-14 01:33:51 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-14 01:33:52 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-14 01:33:52 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-14 01:33:52 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-14 01:33:52 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-14 01:33:52 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-14 01:33:52 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-14 01:33:52 (9251) [INFO] Trying other mirror.
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-14 01:33:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 01:33:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 01:33:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-14 01:33:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-14 01:33:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-14 01:33:52 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 01:33:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-14 01:33:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-14 01:33:52 (9251) [INFO]         or
* 2025-01-14 01:33:52 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 01:33:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 01:33:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 01:33:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 01:33:52 (9251) [INFO]         compromise:
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-14 01:33:52 (9251) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-14 01:33:52 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-14 01:33:52 (9268) [INFO] 
* 2025-01-14 01:33:52 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-14 01:33:52 (5803) [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/
* 2025-01-14 01:33:52 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-14 01:33:52 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-14 01:33:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VfAS4hwHtB/ea_profile.json
* 2025-01-14 01:33:56 (484) [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/VfAS4hwHtB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-14 01:33:56 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-15 01:33:27 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-15 01:33:27 (10313) [INFO] Script is up to date.
* 2025-01-15 01:33:28 (252) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This cannot be upgraded by the native leapp tool.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-01-15 01:33:28 (6225) [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.

* 2025-01-15 01:33:28 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-01-15 01:33:28 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-15 01:33:28 (9238) [INFO] 
* 2025-01-15 01:33:32 (3963) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-01-15 01:33:32 (3970) [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.

* 2025-01-15 01:33:32 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-15 01:33:32 (9238) [INFO] 
* 2025-01-15 01:33:43 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-01-15 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-01-15 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-01-15 01:33:43 (5910) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-15 01:33:43 (5910) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-01-15 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-01-15 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-01-15 01:33:43 (5910) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-01-15 01:33:43 (5934) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-01-15 01:33:43 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-15 01:33:43 (9238) [INFO] 
* 2025-01-15 01:33:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 01:33:43 (9251) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 740671.
* 2025-01-15 01:33:43 (9251) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2025-01-15 01:33:43 (9251) [INFO]   The other application is: yum
* 2025-01-15 01:33:43 (9251) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2025-01-15 01:33:43 (9251) [INFO]     Started: Wed Jan 15 01:33:35 2025 - 00:08 ago
* 2025-01-15 01:33:43 (9251) [INFO]     State  : Sleeping, pid: 740671
* 2025-01-15 01:33:45 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-15 01:33:46 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-15 01:33:46 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-15 01:33:46 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-15 01:33:46 (9251) [INFO]  * epel: mirror.math.princeton.edu
* 2025-01-15 01:33:46 (9251) [INFO]  * remi-php72: mirror.pit.teraswitch.com
* 2025-01-15 01:33:46 (9251) [INFO]  * remi-php73: mirror.pit.teraswitch.com
* 2025-01-15 01:33:46 (9251) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-01-15 01:33:47 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-15 01:33:48 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-15 01:33:48 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-15 01:33:48 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-15 01:33:48 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-15 01:33:48 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-15 01:33:48 (9251) [INFO] Trying other mirror.
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-15 01:33:48 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 01:33:48 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 01:33:48 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-15 01:33:48 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-15 01:33:48 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-15 01:33:48 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 01:33:48 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-15 01:33:48 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-15 01:33:48 (9251) [INFO]         or
* 2025-01-15 01:33:48 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 01:33:48 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 01:33:48 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 01:33:48 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 01:33:48 (9251) [INFO]         compromise:
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-15 01:33:48 (9251) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-15 01:33:48 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-15 01:33:48 (9268) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-15 01:33:48 (5793) [WARN] Initial run of "yum makecache" failed: Existing lock /var/run/yum.pid: another copy is running as pid 740671.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (326 MB VSZ)
    Started: Wed Jan 15 01:33:35 2025 - 00:08 ago
    State  : Sleeping, pid: 740671
Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-15 01:33:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-15 01:33:48 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-15 01:33:48 (9238) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 01:33:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-01-15 01:33:48 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-15 01:33:48 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-15 01:33:48 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-01-15 01:33:48 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-15 01:33:48 (9251) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-01-15 01:33:48 (9251) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-01-15 01:33:48 (9251) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-01-15 01:33:48 (9251) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-15 01:33:48 (9251) [INFO]               : yarn
* 2025-01-15 01:33:48 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-15 01:33:48 (9251) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-01-15 01:33:48 (9268) [INFO] 
* 2025-01-15 01:33:48 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-15 01:33:48 (9238) [INFO] 
* 2025-01-15 01:33:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 01:33:49 (9251) [INFO] Determining fastest mirrors
* 2025-01-15 01:33:51 (9251) [INFO]  * EA4: 185.125.185.32
* 2025-01-15 01:33:51 (9251) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-01-15 01:33:51 (9251) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-01-15 01:33:51 (9251) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-01-15 01:33:51 (9251) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-01-15 01:33:51 (9251) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-01-15 01:33:51 (9251) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-01-15 01:33:51 (9251) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-15 01:33:52 (9251) [INFO] Importing GPG key 0x98AB5139:
* 2025-01-15 01:33:52 (9251) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-01-15 01:33:52 (9251) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-01-15 01:33:52 (9251) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-01-15 01:33:52 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-15 01:33:52 (9251) [INFO] Trying other mirror.
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-01-15 01:33:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 01:33:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 01:33:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-15 01:33:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-15 01:33:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-15 01:33:52 (9251) [INFO]             yum --disablerepo=virtualbox ...
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 01:33:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-15 01:33:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]             yum-config-manager --disable virtualbox
* 2025-01-15 01:33:52 (9251) [INFO]         or
* 2025-01-15 01:33:52 (9251) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 01:33:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 01:33:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 01:33:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 01:33:52 (9251) [INFO]         compromise:
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-01-15 01:33:52 (9251) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-01-15 01:33:52 (9251) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-15 01:33:52 (9268) [INFO] 
* 2025-01-15 01:33:52 (9251) [INFO] Is this ok [y/N]: 
* 2025-01-15 01:33:52 (5803) [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/
* 2025-01-15 01:33:52 (5804) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-01-15 01:33:52 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-15 01:33:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jptCPCCbEc/ea_profile.json
* 2025-01-15 01:33:57 (484) [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/jptCPCCbEc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-15 01:33:57 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-02 01:34:04 (10291) [INFO] Self-update of script version 59 requested.
* 2025-02-02 01:34:05 (10296) [INFO] Newer version of script found. Downloading.
* 2025-02-02 01:34:05 (10305) [INFO] Script update to version 60 successful.
* 2025-02-02 01:34:06 (254) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This script cannot upgrade container environments.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-02-02 01:34:06 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin
option in the sshd_config file. This option may default to "prohibit-password"
after the upgrade is complete. We will set the 'PermitRootLogin' value in
/etc/ssh/sshd_config to 'yes' before upgrading.

* 2025-02-02 01:34:06 (254) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2025-02-02 01:34:08 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-02-02 01:34:08 (254) [WARN] *** 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.51.

* 2025-02-02 01:34:08 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-02 01:34:08 (9401) [INFO] 
* 2025-02-02 01:34:13 (4048) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-02-02 01:34:13 (4055) [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.

* 2025-02-02 01:34:13 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-02 01:34:13 (9401) [INFO] 
* 2025-02-02 01:34:21 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-02-02 01:34:21 (6019) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-02-02 01:34:21 (6019) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-02-02 01:34:21 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-02-02 01:34:21 (5995) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-02-02 01:34:21 (6019) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-02-02 01:34:21 (6019) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-02-02 01:34:21 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-02-02 01:34:21 (6019) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-02-02 01:34:21 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-02 01:34:21 (9401) [INFO] 
* 2025-02-02 01:34:22 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-02 01:34:22 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-02 01:34:23 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-02 01:34:23 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-02 01:34:23 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-02 01:34:23 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-02 01:34:23 (9414) [INFO]  * remi-php72: mirror.pit.teraswitch.com
* 2025-02-02 01:34:23 (9414) [INFO]  * remi-php73: mirror.pit.teraswitch.com
* 2025-02-02 01:34:23 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]  One of the configured repositories failed (Unknown),
* 2025-02-02 01:34:23 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-02 01:34:23 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-02 01:34:23 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-02 01:34:23 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-02 01:34:23 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-02 01:34:23 (9414) [INFO]             yum --disablerepo=<repoid> ...
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-02 01:34:23 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-02 01:34:23 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]             yum-config-manager --disable <repoid>
* 2025-02-02 01:34:23 (9414) [INFO]         or
* 2025-02-02 01:34:23 (9414) [INFO]             subscription-manager repos --disable=<repoid>
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-02 01:34:23 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-02 01:34:23 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-02 01:34:23 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-02 01:34:23 (9414) [INFO]         compromise:
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-02-02 01:34:23 (9414) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2025-02-02 01:34:23 (9414) [INFO]     * free   0 
* 2025-02-02 01:34:23 (9414) [INFO]     * needed 100 k
* 2025-02-02 01:34:23 (9431) [INFO] 
* 2025-02-02 01:34:23 (5878) [WARN] Initial run of "yum makecache" failed: 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2025-02-02 01:34:23 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-02 01:34:23 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-02 01:34:23 (9401) [INFO] 
* 2025-02-02 01:34:23 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-02 01:34:23 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-02-02 01:34:23 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-02 01:34:23 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-02 01:34:23 (9414) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-02-02 01:34:23 (9414) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-02-02 01:34:23 (9414) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-02-02 01:34:23 (9414) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-02-02 01:34:23 (9414) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-02-02 01:34:23 (9414) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-02-02 01:34:23 (9414) [INFO]               : yarn
* 2025-02-02 01:34:23 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-02 01:34:23 (9414) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2025-02-02 01:34:23 (9431) [INFO] 
* 2025-02-02 01:34:23 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-02 01:34:23 (9401) [INFO] 
* 2025-02-02 01:34:24 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-02 01:34:24 (9414) [INFO] Determining fastest mirrors
* 2025-02-02 01:34:26 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-02 01:34:26 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-02 01:34:26 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-02 01:34:26 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-02 01:34:26 (9414) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-02-02 01:34:26 (9414) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-02-02 01:34:26 (9414) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]  One of the configured repositories failed (Unknown),
* 2025-02-02 01:34:26 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-02 01:34:26 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-02 01:34:26 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-02 01:34:26 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-02 01:34:26 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-02 01:34:26 (9414) [INFO]             yum --disablerepo=<repoid> ...
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-02 01:34:26 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-02 01:34:26 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]             yum-config-manager --disable <repoid>
* 2025-02-02 01:34:26 (9414) [INFO]         or
* 2025-02-02 01:34:26 (9414) [INFO]             subscription-manager repos --disable=<repoid>
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-02 01:34:26 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-02 01:34:26 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-02 01:34:26 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-02 01:34:26 (9414) [INFO]         compromise:
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-02-02 01:34:26 (9414) [INFO] 
* 2025-02-02 01:34:26 (9414) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2025-02-02 01:34:26 (9414) [INFO]     * free   0 
* 2025-02-02 01:34:26 (9414) [INFO]     * needed 100 k
* 2025-02-02 01:34:26 (9431) [INFO] 
* 2025-02-02 01:34:26 (5888) [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/
* 2025-02-02 01:34:26 (5889) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2025-02-02 01:34:26 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-02 01:34:28 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9rzgmQVQ75/ea_profile.json
* 2025-02-02 01:34:28 (490) [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/9rzgmQVQ75/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-02 01:34:28 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-03 01:33:24 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-03 01:33:24 (10480) [INFO] Script is up to date.
* 2025-02-03 01:33:25 (254) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This script cannot upgrade container environments.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-02-03 01:33:25 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin
option in the sshd_config file. This option may default to "prohibit-password"
after the upgrade is complete. We will set the 'PermitRootLogin' value in
/etc/ssh/sshd_config to 'yes' before upgrading.

* 2025-02-03 01:33:25 (254) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2025-02-03 01:33:25 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-02-03 01:33:25 (254) [WARN] *** 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.51.

* 2025-02-03 01:33:25 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-03 01:33:25 (9401) [INFO] 
* 2025-02-03 01:33:30 (4048) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-02-03 01:33:30 (4055) [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.

* 2025-02-03 01:33:30 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-03 01:33:30 (9401) [INFO] 
* 2025-02-03 01:33:33 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-02-03 01:33:33 (6019) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-02-03 01:33:33 (6019) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-02-03 01:33:33 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-02-03 01:33:33 (5995) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-02-03 01:33:33 (6019) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-02-03 01:33:33 (6019) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-02-03 01:33:33 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-02-03 01:33:33 (6019) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-02-03 01:33:33 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-03 01:33:33 (9401) [INFO] 
* 2025-02-03 01:33:34 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-03 01:33:34 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-03 01:33:36 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-03 01:33:36 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-03 01:33:36 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-03 01:33:36 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-03 01:33:36 (9414) [INFO]  * remi-php72: mirror.pit.teraswitch.com
* 2025-02-03 01:33:36 (9414) [INFO]  * remi-php73: mirror.pit.teraswitch.com
* 2025-02-03 01:33:36 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]  One of the configured repositories failed (Unknown),
* 2025-02-03 01:33:36 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-03 01:33:36 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-03 01:33:36 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-03 01:33:36 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-03 01:33:36 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-03 01:33:36 (9414) [INFO]             yum --disablerepo=<repoid> ...
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-03 01:33:36 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-03 01:33:36 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]             yum-config-manager --disable <repoid>
* 2025-02-03 01:33:36 (9414) [INFO]         or
* 2025-02-03 01:33:36 (9414) [INFO]             subscription-manager repos --disable=<repoid>
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-03 01:33:36 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-03 01:33:36 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-03 01:33:36 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-03 01:33:36 (9414) [INFO]         compromise:
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-02-03 01:33:36 (9414) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2025-02-03 01:33:36 (9414) [INFO]     * free   0 
* 2025-02-03 01:33:36 (9414) [INFO]     * needed 100 k
* 2025-02-03 01:33:36 (9431) [INFO] 
* 2025-02-03 01:33:36 (5878) [WARN] Initial run of "yum makecache" failed: 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2025-02-03 01:33:36 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-03 01:33:36 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-03 01:33:36 (9401) [INFO] 
* 2025-02-03 01:33:36 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-03 01:33:36 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-02-03 01:33:36 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-03 01:33:36 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-03 01:33:36 (9414) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-02-03 01:33:36 (9414) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-02-03 01:33:36 (9414) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-02-03 01:33:36 (9414) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-02-03 01:33:36 (9414) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-02-03 01:33:36 (9414) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-02-03 01:33:36 (9414) [INFO]               : yarn
* 2025-02-03 01:33:36 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-03 01:33:36 (9414) [INFO] Other repos take up 2.2 M of disk space (use --verbose for details)
* 2025-02-03 01:33:36 (9431) [INFO] 
* 2025-02-03 01:33:36 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-03 01:33:36 (9401) [INFO] 
* 2025-02-03 01:33:37 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-03 01:33:37 (9414) [INFO] Determining fastest mirrors
* 2025-02-03 01:33:40 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-03 01:33:40 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-03 01:33:40 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-03 01:33:40 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-03 01:33:40 (9414) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-02-03 01:33:40 (9414) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-02-03 01:33:40 (9414) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]  One of the configured repositories failed (Unknown),
* 2025-02-03 01:33:40 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-03 01:33:40 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-03 01:33:40 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-03 01:33:40 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-03 01:33:40 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-03 01:33:40 (9414) [INFO]             yum --disablerepo=<repoid> ...
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-03 01:33:40 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-03 01:33:40 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]             yum-config-manager --disable <repoid>
* 2025-02-03 01:33:40 (9414) [INFO]         or
* 2025-02-03 01:33:40 (9414) [INFO]             subscription-manager repos --disable=<repoid>
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-03 01:33:40 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-03 01:33:40 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-03 01:33:40 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-03 01:33:40 (9414) [INFO]         compromise:
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-02-03 01:33:40 (9414) [INFO] 
* 2025-02-03 01:33:40 (9414) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
* 2025-02-03 01:33:40 (9414) [INFO]     * free   0 
* 2025-02-03 01:33:40 (9414) [INFO]     * needed 100 k
* 2025-02-03 01:33:40 (9431) [INFO] 
* 2025-02-03 01:33:40 (5888) [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/
* 2025-02-03 01:33:40 (5889) [ERROR] 

 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

Insufficient space in download directory /var/cache/yum/x86_64/7/EA4
    * free   0 
    * needed 100 k
* 2025-02-03 01:33:40 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-03 01:33:41 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yOVGf7Bt5K/ea_profile.json
* 2025-02-03 01:33:42 (490) [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/yOVGf7Bt5K/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-03 01:33:42 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-02-05 01:33:28 (10458) [INFO] Self-update of script version 60 requested.
* 2025-02-05 01:33:28 (10480) [INFO] Script is up to date.
* 2025-02-05 01:33:29 (254) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This script cannot upgrade container environments.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-02-05 01:33:29 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin
option in the sshd_config file. This option may default to "prohibit-password"
after the upgrade is complete. We will set the 'PermitRootLogin' value in
/etc/ssh/sshd_config to 'yes' before upgrading.

* 2025-02-05 01:33:29 (254) [WARN] *** Elevation Blocker detected: ***
disk space issue
* 2025-02-05 01:33:29 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-02-05 01:33:29 (254) [WARN] *** 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.51.

* 2025-02-05 01:33:29 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-02-05 01:33:29 (9401) [INFO] 
* 2025-02-05 01:33:35 (4048) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-02-05 01:33:35 (4055) [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.

* 2025-02-05 01:33:35 (9400) [INFO] Running: /usr/bin/yum list extras
* 2025-02-05 01:33:35 (9401) [INFO] 
* 2025-02-05 01:33:45 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-02-05 01:33:45 (6019) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-02-05 01:33:45 (6019) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-02-05 01:33:45 (5995) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-02-05 01:33:45 (5995) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-02-05 01:33:45 (6019) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-02-05 01:33:45 (6019) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-02-05 01:33:45 (5995) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-02-05 01:33:45 (6019) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-02-05 01:33:45 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-05 01:33:45 (9401) [INFO] 
* 2025-02-05 01:33:45 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-05 01:33:45 (9414) [INFO] Loading mirror speeds from cached hostfile
* 2025-02-05 01:33:46 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-05 01:33:46 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-05 01:33:46 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-05 01:33:46 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-05 01:33:46 (9414) [INFO]  * remi-php72: mirror.pit.teraswitch.com
* 2025-02-05 01:33:46 (9414) [INFO]  * remi-php73: mirror.pit.teraswitch.com
* 2025-02-05 01:33:46 (9414) [INFO]  * remi-safe: mirror.pit.teraswitch.com
* 2025-02-05 01:33:47 (9414) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-02-05 01:33:47 (9414) [INFO] Importing GPG key 0x98AB5139:
* 2025-02-05 01:33:47 (9414) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-02-05 01:33:47 (9414) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-02-05 01:33:47 (9414) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-02-05 01:33:47 (9414) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-02-05 01:33:47 (9414) [INFO] Trying other mirror.
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-02-05 01:33:47 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-05 01:33:47 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-05 01:33:47 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-05 01:33:47 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-05 01:33:47 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-05 01:33:47 (9414) [INFO]             yum --disablerepo=virtualbox ...
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-05 01:33:47 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-05 01:33:47 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]             yum-config-manager --disable virtualbox
* 2025-02-05 01:33:47 (9414) [INFO]         or
* 2025-02-05 01:33:47 (9414) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-05 01:33:47 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-05 01:33:47 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-05 01:33:47 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-05 01:33:47 (9414) [INFO]         compromise:
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-02-05 01:33:47 (9414) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-02-05 01:33:47 (9414) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-02-05 01:33:47 (9431) [INFO] 
* 2025-02-05 01:33:47 (9414) [INFO] Is this ok [y/N]: 
* 2025-02-05 01:33:47 (5878) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-02-05 01:33:47 (5879) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-02-05 01:33:47 (9400) [INFO] Running: /usr/bin/yum clean all
* 2025-02-05 01:33:47 (9401) [INFO] 
* 2025-02-05 01:33:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-05 01:33:48 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-02-05 01:33:48 (9414) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-02-05 01:33:48 (9414) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-02-05 01:33:48 (9414) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-02-05 01:33:48 (9414) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-02-05 01:33:48 (9414) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-02-05 01:33:48 (9414) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-02-05 01:33:48 (9414) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-02-05 01:33:48 (9414) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-02-05 01:33:48 (9414) [INFO]               : yarn
* 2025-02-05 01:33:48 (9414) [INFO] Cleaning up list of fastest mirrors
* 2025-02-05 01:33:48 (9414) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-02-05 01:33:48 (9431) [INFO] 
* 2025-02-05 01:33:48 (9400) [INFO] Running: /usr/bin/yum makecache
* 2025-02-05 01:33:48 (9401) [INFO] 
* 2025-02-05 01:33:48 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-02-05 01:33:48 (9414) [INFO] Determining fastest mirrors
* 2025-02-05 01:33:51 (9414) [INFO]  * EA4: 185.125.185.32
* 2025-02-05 01:33:51 (9414) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-02-05 01:33:51 (9414) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-02-05 01:33:51 (9414) [INFO]  * epel: mirror.math.princeton.edu
* 2025-02-05 01:33:51 (9414) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-02-05 01:33:51 (9414) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-02-05 01:33:51 (9414) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-02-05 01:33:52 (9414) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-02-05 01:33:52 (9414) [INFO] Importing GPG key 0x98AB5139:
* 2025-02-05 01:33:52 (9414) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-02-05 01:33:52 (9414) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-02-05 01:33:52 (9414) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-02-05 01:33:52 (9414) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-02-05 01:33:52 (9414) [INFO] Trying other mirror.
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-02-05 01:33:52 (9414) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-02-05 01:33:52 (9414) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-02-05 01:33:52 (9414) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-02-05 01:33:52 (9414) [INFO]         distribution release than is supported by the repository (and the
* 2025-02-05 01:33:52 (9414) [INFO]         packages for the previous distribution release still work).
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-02-05 01:33:52 (9414) [INFO]             yum --disablerepo=virtualbox ...
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-02-05 01:33:52 (9414) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-02-05 01:33:52 (9414) [INFO]         again or use --enablerepo for temporary usage:
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]             yum-config-manager --disable virtualbox
* 2025-02-05 01:33:52 (9414) [INFO]         or
* 2025-02-05 01:33:52 (9414) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-02-05 01:33:52 (9414) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-02-05 01:33:52 (9414) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-02-05 01:33:52 (9414) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-02-05 01:33:52 (9414) [INFO]         compromise:
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-02-05 01:33:52 (9414) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-02-05 01:33:52 (9414) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-02-05 01:33:52 (9431) [INFO] 
* 2025-02-05 01:33:52 (9414) [INFO] Is this ok [y/N]: 
* 2025-02-05 01:33:52 (5888) [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/
* 2025-02-05 01:33:52 (5889) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-02-05 01:33:52 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-02-05 01:33:53 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UJ8ph7CErP/ea_profile.json
* 2025-02-05 01:33:56 (490) [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/UJ8ph7CErP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-02-05 01:33:56 (454) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-04-03 01:33:39 (10458) [INFO] Self-update of script version 60 requested.
* 2025-04-03 01:33:39 (10463) [INFO] Newer version of script found. Downloading.
* 2025-04-03 01:33:40 (10472) [INFO] Script update to version 63 successful.
* 2025-04-03 01:33:41 (259) [WARN] *** Elevation Blocker detected: ***
cPanel thinks that this is a container-like environment.
This script cannot upgrade container environments.
Consider contacting your hypervisor provider for alternative solutions.

* 2025-04-03 01:33:41 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin
option in the sshd_config file. This option may default to "prohibit-password"
after the upgrade is complete. We will set the 'PermitRootLogin' value in
/etc/ssh/sshd_config to 'yes' before upgrading.

* 2025-04-03 01:33:41 (259) [WARN] *** Elevation Blocker detected: ***
cPanel does not detect a valid license for itself on the system at this
time. This could cause problems during the update.

cPanel expects to find a license for the IP address 216.158.237.236.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2025-04-03 01:33:41 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2025-04-03 01:33:41 (259) [WARN] *** 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.55.

* 2025-04-03 01:33:41 (9921) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-04-03 01:33:41 (9922) [INFO] 
* 2025-04-03 01:33:46 (4381) [WARN] You have MySQL 5.7 installed.
This version is not available for AlmaLinux 8.

* 2025-04-03 01:33:46 (4388) [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.

* 2025-04-03 01:33:46 (9921) [INFO] Running: /usr/bin/yum list extras
* 2025-04-03 01:33:46 (9922) [INFO] 
* 2025-04-03 01:34:03 (6385) [ERROR] 1 package(s) installed from unsupported YUM repo 'yarn' from /etc/yum.repos.d/yarn.repo
* 2025-04-03 01:34:03 (6409) [INFO] Unsupported YUM repo enabled 'remi-php72' without packages installed from /etc/yum.repos.d/remi-php72.repo, these will be disabled before ELevation
* 2025-04-03 01:34:03 (6409) [INFO] Unsupported YUM repo enabled 'mongodb-org-4.0' without packages installed from /etc/yum.repos.d/mongodb-org-4.0.repo, these will be disabled before ELevation
* 2025-04-03 01:34:03 (6385) [ERROR] 2 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-04-03 01:34:03 (6385) [ERROR] 9 package(s) installed from unsupported YUM repo 'mongodb-org-5.0' from /etc/yum.repos.d/mongodb-org.repo
* 2025-04-03 01:34:03 (6409) [INFO] Unsupported YUM repo enabled 'remi-php73' without packages installed from /etc/yum.repos.d/remi-php73.repo, these will be disabled before ELevation
* 2025-04-03 01:34:03 (6409) [INFO] Unsupported YUM repo enabled 'nodesource' without packages installed from /etc/yum.repos.d/nodesource-el7.repo, these will be disabled before ELevation
* 2025-04-03 01:34:03 (6385) [ERROR] 1 package(s) installed from unsupported YUM repo 'virtualbox' from /etc/yum.repos.d/virtualbox.repo
* 2025-04-03 01:34:03 (6409) [INFO] Unsupported YUM repo enabled 'remi-safe' without packages installed from /etc/yum.repos.d/remi-safe.repo, these will be disabled before ELevation
* 2025-04-03 01:34:03 (9921) [INFO] Running: /usr/bin/yum makecache
* 2025-04-03 01:34:03 (9922) [INFO] 
* 2025-04-03 01:34:03 (9935) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-04-03 01:34:03 (9935) [INFO] Loading mirror speeds from cached hostfile
* 2025-04-03 01:34:04 (9935) [INFO]  * EA4: 185.125.185.32
* 2025-04-03 01:34:04 (9935) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-04-03 01:34:04 (9935) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-04-03 01:34:04 (9935) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-04-03 01:34:04 (9935) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-04-03 01:34:04 (9935) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-04-03 01:34:04 (9935) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-04-03 01:34:07 (9935) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-04-03 01:34:07 (9935) [INFO] Importing GPG key 0x98AB5139:
* 2025-04-03 01:34:07 (9935) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-04-03 01:34:07 (9935) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-04-03 01:34:07 (9935) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-04-03 01:34:07 (9935) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-04-03 01:34:07 (9935) [INFO] Trying other mirror.
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-04-03 01:34:07 (9935) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-04-03 01:34:07 (9935) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-04-03 01:34:07 (9935) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-04-03 01:34:07 (9935) [INFO]         distribution release than is supported by the repository (and the
* 2025-04-03 01:34:07 (9935) [INFO]         packages for the previous distribution release still work).
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-04-03 01:34:07 (9935) [INFO]             yum --disablerepo=virtualbox ...
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-04-03 01:34:07 (9935) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-04-03 01:34:07 (9935) [INFO]         again or use --enablerepo for temporary usage:
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]             yum-config-manager --disable virtualbox
* 2025-04-03 01:34:07 (9935) [INFO]         or
* 2025-04-03 01:34:07 (9935) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-04-03 01:34:07 (9935) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-04-03 01:34:07 (9935) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-04-03 01:34:07 (9935) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-04-03 01:34:07 (9935) [INFO]         compromise:
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-04-03 01:34:07 (9935) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-04-03 01:34:07 (9935) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-04-03 01:34:07 (9952) [INFO] 
* 2025-04-03 01:34:07 (9935) [INFO] Is this ok [y/N]: 
* 2025-04-03 01:34:07 (6267) [WARN] Initial run of "yum makecache" failed: Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-04-03 01:34:07 (6268) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-04-03 01:34:07 (9921) [INFO] Running: /usr/bin/yum clean all
* 2025-04-03 01:34:07 (9922) [INFO] 
* 2025-04-03 01:34:08 (9935) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-04-03 01:34:08 (9935) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 451607.
* 2025-04-03 01:34:08 (9935) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2025-04-03 01:34:08 (9935) [INFO]   The other application is: yum
* 2025-04-03 01:34:08 (9935) [INFO]     Memory :  35 M RSS (326 MB VSZ)
* 2025-04-03 01:34:08 (9935) [INFO]     Started: Thu Apr  3 01:33:56 2025 - 00:12 ago
* 2025-04-03 01:34:08 (9935) [INFO]     State  : Sleeping, pid: 451607
* 2025-04-03 01:34:10 (9935) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2025-04-03 01:34:10 (9935) [INFO]   The other application is: yum
* 2025-04-03 01:34:10 (9935) [INFO]     Memory :  39 M RSS (549 MB VSZ)
* 2025-04-03 01:34:10 (9935) [INFO]     Started: Thu Apr  3 01:33:56 2025 - 00:14 ago
* 2025-04-03 01:34:10 (9935) [INFO]     State  : Sleeping, pid: 451607
* 2025-04-03 01:34:12 (9935) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base
* 2025-04-03 01:34:12 (9935) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-04-03 01:34:12 (9935) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-04-03 01:34:12 (9935) [INFO]               : centos7els-rollout-6 docker-ce-stable epel extras imunify360
* 2025-04-03 01:34:12 (9935) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-04-03 01:34:12 (9935) [INFO]               : imunify360-rollout-4 mongodb-org-4.0 mongodb-org-5.0
* 2025-04-03 01:34:12 (9935) [INFO]               : mysql-connectors-community mysql-tools-community
* 2025-04-03 01:34:12 (9935) [INFO]               : mysql57-community nodesource remi-php72 remi-php73 remi-safe
* 2025-04-03 01:34:12 (9935) [INFO]               : updates virtualbox wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-04-03 01:34:12 (9935) [INFO]               : yarn
* 2025-04-03 01:34:12 (9935) [INFO] Cleaning up list of fastest mirrors
* 2025-04-03 01:34:12 (9935) [INFO] Other repos take up 2.3 M of disk space (use --verbose for details)
* 2025-04-03 01:34:12 (9952) [INFO] 
* 2025-04-03 01:34:12 (9921) [INFO] Running: /usr/bin/yum makecache
* 2025-04-03 01:34:12 (9922) [INFO] 
* 2025-04-03 01:34:12 (9935) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-04-03 01:34:12 (9935) [INFO] Determining fastest mirrors
* 2025-04-03 01:34:14 (9935) [INFO]  * EA4: 185.125.185.32
* 2025-04-03 01:34:14 (9935) [INFO]  * cpanel-addons-production-feed: 185.125.185.32
* 2025-04-03 01:34:14 (9935) [INFO]  * cpanel-plugins: 185.125.185.32
* 2025-04-03 01:34:14 (9935) [INFO]  * epel: d2lzkl7pfhq30w.cloudfront.net
* 2025-04-03 01:34:14 (9935) [INFO]  * remi-php72: repo1.ash.innoscale.net
* 2025-04-03 01:34:14 (9935) [INFO]  * remi-php73: repo1.ash.innoscale.net
* 2025-04-03 01:34:14 (9935) [INFO]  * remi-safe: repo1.ash.innoscale.net
* 2025-04-03 01:34:15 (9935) [INFO] Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-04-03 01:34:15 (9935) [INFO] Importing GPG key 0x98AB5139:
* 2025-04-03 01:34:15 (9935) [INFO]  Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
* 2025-04-03 01:34:15 (9935) [INFO]  Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
* 2025-04-03 01:34:15 (9935) [INFO]  From       : https://www.virtualbox.org/download/oracle_vbox.asc
* 2025-04-03 01:34:15 (9935) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-04-03 01:34:15 (9935) [INFO] Trying other mirror.
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]  One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
* 2025-04-03 01:34:15 (9935) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-04-03 01:34:15 (9935) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-04-03 01:34:15 (9935) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-04-03 01:34:15 (9935) [INFO]         distribution release than is supported by the repository (and the
* 2025-04-03 01:34:15 (9935) [INFO]         packages for the previous distribution release still work).
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-04-03 01:34:15 (9935) [INFO]             yum --disablerepo=virtualbox ...
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-04-03 01:34:15 (9935) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-04-03 01:34:15 (9935) [INFO]         again or use --enablerepo for temporary usage:
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]             yum-config-manager --disable virtualbox
* 2025-04-03 01:34:15 (9935) [INFO]         or
* 2025-04-03 01:34:15 (9935) [INFO]             subscription-manager repos --disable=virtualbox
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-04-03 01:34:15 (9935) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-04-03 01:34:15 (9935) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-04-03 01:34:15 (9935) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-04-03 01:34:15 (9935) [INFO]         compromise:
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO]             yum-config-manager --save --setopt=virtualbox.skip_if_unavailable=true
* 2025-04-03 01:34:15 (9935) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO] failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
* 2025-04-03 01:34:15 (9935) [INFO] http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-04-03 01:34:15 (9952) [INFO] 
* 2025-04-03 01:34:15 (9935) [INFO] Is this ok [y/N]: 
* 2025-04-03 01:34:15 (6277) [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/
* 2025-04-03 01:34:15 (6278) [ERROR] Importing GPG key 0x98AB5139:
 Userid     : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
 Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
 From       : https://www.virtualbox.org/download/oracle_vbox.asc
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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=virtualbox ...

     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 virtualbox
        or
            subscription-manager repos --disable=virtualbox

     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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
* 2025-04-03 01:34:16 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-04-03 01:34:17 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iR1uXh58Dw/ea_profile.json
* 2025-04-03 01:34:20 (535) [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/iR1uXh58Dw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043.
* 2025-04-03 01:34:20 (476) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/

Zerion Mini Shell 1.0